canon-upkeep
Skill2 starsChanged 28 days agoMITView on GitHub
Bring the repo's rules file, repo map, and pattern index back in line with the code. Use monthly, after a large refactor, or when the user says the rules feel stale or the agent keeps tripping on outdated docs.
In this repository6 other files it gives its agents.
- templates/AGENTS.mdAGENTS.md
- templates/CLAUDE.mdCLAUDE.md
- absence-checkSkill
- harness-setupSkill
- independent-reviewSkill
- pattern-cardSkill
The file
We split this skill into the rules it gives an agent
1 rule. About 0 are common, 1 is distinctive, and 0 are 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.
0
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Distinctive: line 19
Check the size budget: the always-loaded rules file stays under ~150 lines.
≈ “Common” is an estimate: at least 1 in 5 of the 350,495 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
Keep the canon current
A rules file that drifts from the repo becomes noise, and a stale fact gets quoted as true.
Steps
- Find when the canon last changed:
git log -1 --format=%ad -- AGENTS.md docs/REPO_MAP.md. - Survey what changed since then:
git log --since=<that date> --stat, new or moved modules, retired code. - Propose updates from measured facts only:
docs/REPO_MAP.mdrows, names, and runtime values, each re-measured with its command;- rules that no longer match how the repo works;
- counts or versions that crept into docs - replace with the command that produces them.
- Check the size budget: the always-loaded rules file stays under ~150 lines. Move facts to the repo map, area knowledge to on-demand files, and enforceable rules to hooks.
- Grep for each changed rule's key phrase across the repo. A rule stated in two files is edited in both or replaced by a link.
- Show the diff. Never weaken the top invariant, and never delete a rule only because you do not understand it - ask.
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.