pre-compact SKILL.md skillA
pre-compact from chrisallenlane/claude-swe-workflows is an agent skill: a SKILL.md folder an AI agent loads when a task calls for it.
mdr add chrisallenlane/claude-swe-workflows/pre-compact@git:20261116.75ffff6Pins git:20261116.75ffff6 in mdr.lock. Pin the fingerprint instead.
- Audit grade
- A, 17 of 17 checks passed
- Kind
- SKILL.md skill
- Repository
- chrisallenlane/claude-swe-workflows
- Path
skills/pre-compact/SKILL.md- Versions recorded
- 3
- Latest version
- git:20261116.75ffff6, committed Nov 16, 2026
- First version recorded
- May 8, 2026
- Size
- 6,147 bytes
- Repository stars
- 21
- License
- MIT
Pre-compaction housekeeping. Updates persistent memory, checks git hygiene and trash, produces an SBAR with a go/no-go recommendation, and emits a resume prompt if work remains. Run immediately before /compact.
Collected from public GitHub. Every version is saved exactly as it was and never changes. Install it at an exact version with the mdr tool, and every file is checked before it reaches your agent. The main file is checked against the SHA-256 fingerprint recorded here, and the others against the fingerprints GitHub keeps for its source commit. The automatic checks below grade the latest version, and the same checks always give the same file the same grade.
What the file says
# Pre-Compact - Session Housekeeping Before Compaction The user is about to run `/compact`. Compaction destroys conversation context. Anything important from this session that is not persisted somewhere durable — memory files, commits, tickets, code, the issue tracker — is lost. This skill is the last-chance pass to capture session state. Walk a fixed checklist as a floor, then use judgment for anything the checklist does not anticipate, and end with an SBAR-formatted go/no-go report. ## Philosophy **Persist before you compact; ask rather than guess.** What will matter next session goes into memory, a commit (with permission), or the SBAR. When unsure whether something is trash, abandoned, or important, ask the user. ## Workflow ### 1. Persistent memory pass Updating persistent memory is the core reason this skill exists. The user invokes `/pre-compact` *because* they want memory written before compaction. Do not skip this step or treat it as conditional. Re-scan the session for facts worth saving across conversations. Follow the memory conventions in effect; update rather than duplicate. ### 2. Git hygiene pass Run `git status` and assess: …
Read the whole file at its exact version.
How to install
claude plugin marketplace add https://markdownregistry.com/mp/a/art_2xbz54fwy5bmtlm2/06e514db1f20d7ecabd996e860e488de69f75b7ea7a582e57076f18863e61816.json
Then /plugin install pre-compact@markdownregistry-2xbz54fwy5bmtlm2 in Claude Code. It installs git:20261116.75ffff6, the one graded A here, pinned to the commit it was graded at, and leaves it there.
mdr add chrisallenlane/claude-swe-workflows/pre-compact@sha256:06e514db1f20d7ecThe line at the top of this page pins the label git:20261116.75ffff6, which is what most people want. This one pins the sha256 fingerprint of the contents instead, so it survives a label being moved. Either way the exact version is written to mdr.lock, and mdr install downloads and checks those contents again, so it installs them exactly or stops with an error.
[](https://markdownregistry.com/a/art_2xbz54fwy5bmtlm2)
2 badge image fetches in 30 days. What the badge shows.
claude mcp add --transport http markdownregistry https://markdownregistry.com/mcp/registry
Then ask it: what changed in chrisallenlane/claude-swe-workflows/pre-compact since the version I have? It reads every saved version here, no key and no account. Any agent that speaks MCP can add it.
Got a copy of pre-compact from somewhere else? Ask it: where did my pre-compact come from, and what was changed? It names the public original, the version yours is closest to and every changed line. The text is not kept.
Versions
The registry has recorded 3 versions of this file, between May 8, 2026 and Nov 16, 2026, about one every 96 days.
Watch this file (sign in, one email per new version)
| version | committed | commit | size | audit | |
|---|---|---|---|---|---|
| git:20261116.75ffff6 latest | 2026-11-16 | 75ffff6 | 6,147 B | A | view · diff |
| git:20261116.e39effb | 2026-11-16 | e39effb | 6,243 B | A | view · diff |
| git:20260508.343c16c | 2026-05-08 | 343c16c | 7,588 B | A | view |
Committed this skill to a repository? Install the markdownregistry skill updates app on it, or on all of them. When the registry saves a newer version, a pull request brings your copy to it within minutes, the newest version first, then what changed and any check it newly trips. A copy you edited is never touched, and nothing is deleted.
It asks to read and write contents and pull requests, and to read metadata. No workflow file, no Actions setting, nothing runs on your runners. Uninstall it and everything the registry kept about your repository is deleted.
Committed this skill to a repository? Add one workflow file, and when a newer version is saved, a pull request brings your copy to it, the newest version first, then what changed and any check it newly trips. A copy you edited is never touched, and nothing is deleted.
mkdir -p .github/workflows && curl -fsSL https://markdownregistry.com/ci/skill-updates.yml -o .github/workflows/skill-updates.yml
It runs daily on GitHub Actions, no key and no account. Read the workflow before you add it.
Installed this file, say at .claude/skills/pre-compact/SKILL.md? Drop it here to learn which saved version you have and what changed since. Your browser works out its SHA-256 fingerprint and sends only that; the file itself never leaves your computer.
Or paste its contents
Your agent can run this same check on the agent markdown files you have installed, up to 50 in one ask. Add the registry once:
claude mcp add --transport http markdownregistry https://markdownregistry.com/mcp/registry
Then ask it to check the files you have installed. No key and no account.
From the root of your project, one line hashes each installed skill's SKILL.md, your AGENTS.md and your CLAUDE.md, and asks the registry once. Only the fingerprints and paths are sent.
sha256sum .claude/skills/*/SKILL.md AGENTS.md CLAUDE.md | curl -s --data-binary @- https://markdownregistry.com/api/v1/check-copies
In CI, add --fail-with-body: the answer is 409 when any file is behind, so the step fails and still prints which files.
sha256sum .claude/skills/*/SKILL.md AGENTS.md CLAUDE.md | curl -s --fail-with-body --data-binary @- https://markdownregistry.com/api/v1/check-copies
No sha256sum on your machine? shasum -a 256 prints the same lines.
Audit of the latest version
- pass: Frontmatter block present
- pass: Frontmatter declares a name
- pass: Frontmatter declares a description
- pass: Size between 200 bytes and 200 KB (6147 bytes)
- pass: No zero-width or bidi control characters
- pass: No instruction hidden inside an HTML comment
- pass: No link to an exfiltration or paste host
- pass: No credential-shaped string
- pass: No instruction to send local credentials anywhere
- pass: No text hidden with inline styles
- pass: No prompt-injection phrasing
- pass: No curl or wget piped into a shell
- pass: No recursive delete of root, home or parent
- pass: No instruction to read or print local credentials
- pass: No base64 blob over 200 characters
- pass: No link to a raw IP address
- pass: No script tag
Source
chrisallenlane/claude-swe-workflows · 21 stars · license MIT · pushed 2026-11-17 · branch master
API
GET https://markdownregistry.com/api/v1/artifacts/art_2xbz54fwy5bmtlm2 GET https://markdownregistry.com/api/v1/resolve?ref=chrisallenlane/claude-swe-workflows/pre-compact GET https://markdownregistry.com/api/v1/blob/06e514db1f20d7ecabd996e860e488de69f75b7ea7a582e57076f18863e61816
Your AI assistant does the legwork. You hear about the deals worth your word. Hand yours the standing instructions at modelranch.com and it joins the network that reads files like this one.
Guides: the SKILL.md format and its required fields · what to check before you install a skill · how to pin a skill to an exact version · where to find agent skills · keeping a team on the same skills · which agent file does what.
More from chrisallenlane/claude-swe-workflows
Every file in chrisallenlane/claude-swe-workflows