dx-archive
Skill8 starsChanged 4 months agoMITView on GitHub
Archive a completed change or effort — move its folder to context/archive/ and stamp it archived.
In this repository21 other files it gives its agents.
- CLAUDE.mdCLAUDE.md
- dx-brainstormSkill
- dx-diagnoseSkill
- dx-distillSkill
- dx-domain-discoverSkill
- dx-domainSkill
- dx-frameSkill
- dx-implementSkill
- dx-initSkill
- dx-lessonSkill
- dx-newSkill
- dx-planSkill
- dx-refactor-discoverSkill
- dx-referencesSkill
- dx-researchSkill
- dx-reviewSkill
- dx-review-triageSkill
- dx-roadmapSkill
- dx-standards-discoverSkill
- dx-standards-updateSkill
- dx-tddSkill
The file
We split this skill into the rules it gives an agent
2 rules. About 0 are common, 1 is distinctive, and 1 is very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈1
Distinctive · estimate
This author's own choices. Worth a look.
1
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Distinctive: line 11
Guard: If the id resolves to nothing, or the folder can't move cleanly, do nothing and say why.
- Very specific: line 43
If it was an effort, add one line noting how many child changes it closed.
≈ “Common” is an estimate: at least 1 in 5 of the 372,429 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Files
dx-archive
Retire a finished container. One id in, one folder moved, one stamp written. No registry — the archive is just where done work lives.
Guard. If the id resolves to nothing, or the folder can't move cleanly, do nothing and say why. Never half-move.
Resolve
The argument is one id. Find its home:
context/changes/<id>/→ it's a change.context/efforts/<id>/→ it's an effort.- Neither, or both → fail loud: print what you looked for and stop. (Already under
context/archive/? Say it's already archived.)
Effort gate — children first
An effort is done only when every child change is already archived. Before moving an effort, read its roadmap.md, and for each linked child change check for archived_at (derive it — scan the child's change.md, don't trust a checkbox). If any child is still open, list them and ask before continuing. The user may override.
Review gate — unresolved findings
Scan every reviews/*.md in the container except the legacy impl-review.md and plan-review.md, which triage no longer reads. For each report with any finding marked Resolution: PENDING, warn — "N unresolved finding(s) in reviews/<policy-id>.md — /dx-review-triage <id> <policy-id> to address them first" — and ask whether to archive anyway. The user may override.
Move and stamp
- Destination:
context/archive/<today>-<id>/where<today>isdate +%F. If it already exists, fail loud and stop. - Stamp the moved container's
change.md(oreffort.md): setstatus: archivedandarchived_at:to today's date (date +%F, same format ascreated/updated— no other field in the schema carries a finer timestamp); bumpupdated:. Leave every other field alone. For the exact schema, invokedx-referenceswith topicchange-md(a change) oreffort-md(an effort). - Move the whole folder: prefer
git mvso history follows; fall back tomv(warn) if git is unavailable. Confirm the source is gone and the destination exists — if not, print a diagnostic and stop.
Done when
The folder lives at context/archive/<today>-<id>/, its identity file reads status: archived with archived_at set, and nothing remains under the old path. Print:
✓ Archived <id> → context/archive/<today>-<id>/If it was an effort, add one line noting how many child changes it closed. Then suggest a next step (/dx-new <idea> to start fresh) and stop. Do not chain.
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.

