audit-rules
Skill0 starsChanged 4 months agoMITView on GitHub
Check all rule files against current codebase for staleness
2 other projects use a version of this.
Adopted by
Most recently taken up by
- quietmachineworks/qmwtheir own version, first seen Sep 12, 2026
- fullymiddleaged/Clawnesstheir own version, first seen Jul 28, 2026
Other versions2 projects use a version of this.
Word for word · 0
None found.
Edited · 0
None found.
Wrote their own version · 2
- fullymiddleaged/Clawness★ 5same name
- quietmachineworks/qmw★ 0same name
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 repository21 other files it gives its agents.
- add-to-claudeSkill
- add-to-rulesSkill
- audit-claudeSkill
- autopilotSkill
- better-planSkill
- design-autoSkill
- designSkill
- execute-autoSkill
- executeSkill
- facts-extSkill
- factsSkill
- questionsSkill
- research-autoSkill
- researchSkill
- review-autoSkill
- structure-autoSkill
- structureSkill
- wiki-captureSkill
- wiki-ingestSkill
- wiki-lintSkill
- wiki-querySkill
The file
We split this skill into the rules it gives an agent
3 rules. About 0 are common, 3 are distinctive, and 0 are very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈3
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 8
Read the rule file.
- Distinctive: line 19
After checking all files, output a summary table:
- Distinctive: line 30
Do NOT modify any rule files.
≈ “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
Audit every rule file in .claude/rules/ against the current state of the codebase. For each rule file:
- Read the rule file.
- For each concrete claim (package names, patterns, constants, file paths, conventions), verify it against the code:
- Package/import claims: grep for the import pattern. Does it still exist? Has it changed?
- Pattern claims (e.g., "Route wraps Screen"): check 2-3 actual files that should follow the pattern. Do they?
- Constant claims (e.g., "max 5 devices", "30 min access token"): grep for the value. Still correct?
- Path claims (e.g., "strings in values/strings.xml"): check the path exists.
- Negative claims (e.g., "never use X"): grep for X. Any violations?
- Classify each claim as:
- CONFIRMED — evidence found in current code
- STALE — code contradicts the rule
- UNVERIFIABLE — can't confirm from code alone (e.g., behavioral rules)
- After checking all files, output a summary table:
| Rule File | Total Claims | Confirmed | Stale | Unverifiable |- For any STALE claims, show:
- The rule text
- What the code actually shows
- A suggested update
Do NOT modify any rule files. Report only.
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.