compile
Skill10 starsChanged 4 months agoMITView on GitHub
Serialize the current session into durable state — the breadcrumb the next session resumes from. Use at the end of a work session or after any real advance. Returns working title, objective, decisions, artifacts, defects/risks, open loops, next action, next command, retrieval tags, and a one-sentence memory. Only keeps information that changes future behavior.
13 other projects use a version of this.
Adopted by
Most recently taken up by
- Samuel0101010/wisp-rulecasttheir own version, first seen Oct 20, 2026
- Andamio-Platform/coachtheir own version, first seen Oct 13, 2026
- jtenniswood/espframetheir own version, first seen Oct 8, 2026
- jtenniswood/esphome-media-playertheir own version, first seen Oct 8, 2026
- alibaba/loongcollectortheir own version, first seen Oct 8, 2026
- jtenniswood/espcontroltheir own version, first seen Oct 8, 2026
Used with
Projects with it also use expert-reset, updates and 2 more.
Other files people use alongside this one.
Files found in the same public projects as a version of this one, more often than they turn up anywhere else. Each project counts once, large collections count for less, and this file's own repository is left out.
jtenniswoodSkillexpert-reset
Reimagine this repository from first principles using the current product and user experience as the target. Use when the user says "/expert-reset", asks how the project should be rebuilt if starting again, wants bold architecture or component-structure recommendations, or wants a research-only reset plan unconstrained by current implementation details.
Also in 3 projects that use this
jtenniswoodSkillupdates
Summarize user-facing project updates from the last 7 days, ordered by importance and written as one-sentence "Feature: description" entries. Use when the user says "/updates", asks what changed recently, or wants a concise list of recent features, device support, fixes that users will notice, or other product value.
Also in 3 projects that use this
MicrosoftSkillpr-review
Verify the technical accuracy of a vscode-docs pull request against the VS Code source code in microsoft/vscode. Use when reviewing a docs PR for factual correctness: setting names, command IDs, default values, API shapes, keybindings, versioned availability, and described behavior.
Also in 3 projects that use this
MicrosoftSkillrelease
Use ONLY when the user explicitly asks to cut/publish a Huabu desktop release or tag a version. Performs an outward action — bumps the version in apps/desktop/package.json, commits + annotated-tags vX.Y.Z, and pushes the branch + tag. That tag push auto-builds the macOS/Windows installers and publishes a GitHub Release. Provides `status`, `bump`, `tag-push`, and a one-command `run` (bump → tag-push).
Also in 4 projects that use this
Other versions13 projects use a version of this.
Word for word · 0
None found.
Edited · 0
None found.
Wrote their own version · 13
- apache/skywalking★ 25ksame name
- alibaba/loongcollector★ 2.2ksame name
- jtenniswood/espcontrol★ 1.2ksame name
- jtenniswood/esphome-media-player★ 235same name
- jtenniswood/espframe★ 207same name
- maxwellsdm1867/wheeler★ 12same name
- anatoly-tech/obsidian-skills★ 9same name
- Andamio-Platform/coach★ 6same name
- clearsmog/claude-skills★ 2same name
- sameerhimati/claude-code-kit★ 1same name
3 more not listed
How matches are found. Word for word: the exact same text. Edited: shares passages with this file (“99% same” means 99% of its five-word phrases also appear here; 10% or more counts). Their own version: similar meaning, or, weakest, the same name. We can’t tell which project had it first. Projects are counted among the 200 most-starred candidates, and mentions are links to the repository we found, up to 50 per site, so both counts are a floor.
In this repository24 other files it gives its agents.
The file
Files
/ratchet:compile — the state compiler
A session that isn't compiled evaporates. This command writes the breadcrumb: the compact record that lets the next agent — or you after a context reset — resume without re-deriving anything. Persistence has compression discipline: only what changes future behavior survives.
Step 0 — Load current state
ratchet status --jsonExtend the existing record; do not overwrite it. For a heavy session, delegate to the
ratchet-scribe subagent.
What to serialize (and nothing else)
Save only: decisions, artifacts, defects, open loops, next action, next prompt. Delete interesting-but-nonoperative commentary. If it won't change a future move, it doesn't go in.
- Working title — a handle you'd recognize in a list of sessions.
- Current objective — the locked target, one line.
- Decisions made — actual commitments, with the rejected tempting option and tripwire.
- Artifacts created — title, kind, status, path, known holes.
- Defects / risks found — severity + summary + status.
- Open loops — what's unfinished and what would close it.
- Next action — the single immediate move.
- Next prompt/command — the exact
/ratchet:...to run next. - Retrieval tags — comma-separated handles for future search.
- One-sentence memory — the single line worth saving. Make it load-bearing.
Serialize (write it all through the CLI)
ratchet state set title "<working title>"
ratchet state set nextAction "<single next move>"
ratchet state set nextCommand "/ratchet:<command>"
ratchet state append decisions '{"choice":"...","rejected":"...","tripwire":"..."}' # if any new
ratchet artifact add '{"title":"...","kind":"...","status":"...","holes":["..."]}' # if any new
ratchet defect add '{"severity":"...","summary":"...","artifact":"<id>"}' # if any new
ratchet state append openLoops '{"text":"..."}' # if any
ratchet state set phase compile
ratchet compile doneA defect is born open — the CLI refuses a terminal birth status. Clearing one is a
transition with proof: ratchet defect resolve <id> --evidence "...".
ratchet compile done clears the dirty flag, stamps lastCompileAt, and records a
compile.done history event in one atomic move — which silences the Stop-hook nag. (Run it
last: a state set after it would re-dirty the session.)
CHECKPOINT is not CLOSED. compile done prints CHECKPOINTED, NOT CLOSED and the next
required transition, because serializing says the record is current — never that the work
is finished. An artifact is finished only when a KEEP is bound to its exact revision and
you run:
ratchet artifact close <id>Report the checkpoint as a checkpoint. If the run also closed the artifact, say CLOSED and name the proof id; otherwise say what closing still needs. Then emit the record:
ratchet export markdownOutput contract
Return the exported markdown, followed by:
ONE-SENTENCE MEMORY: <the single priming line>
RETRIEVAL TAGS: <comma,separated,handles>
NEXT: <action> → /ratchet:<command>The ratchet only advances if state advances. Compile is how the turn becomes permanent.
Does it work?
Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.
No reviews yet
People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.
- It worked
- Partly
- It didn't
Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.
Your trail
Files you open will collect here, so you can find them again.
Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.
Now do this for your own.
Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.

