consistency-audit
Skill4 starsChanged 40 days agoNo licenceView on GitHub
Audit a codebase for the same thing built more than once — duplicated components, helpers, patterns, conventions — and settle each one with the user as deliberate (comment it at the code) or accidental (list it as a backlog to unify), optionally unifying afterwards. Use whenever someone says a project has grown inconsistent, asks to find duplicate or copy-pasted components, wants "similar features that don't reuse the same component" found, asks for a reuse / DRY / consistency pass, or wants to know where a shared helper exists but isn't used. Also use when they ask to check whether other places in a repo have the same class of problem as a bug just fixed. Not for a single-file refactor or a one-off "is there a helper for X" lookup.
4 other projects use a version of this.
Adopted by
Most recently taken up by
- Sunnyshinnny776/pm-agentic-cookbooktheir own version, first seen Oct 20, 2026
- igorkravcenko/snowshoetheir own version, first seen Oct 13, 2026
- wanshuiyin/Anti-Autoresearchtheir own version, first seen Jun 27, 2026
- 45ck/hci-review-skilltheir own version, first seen Mar 28, 2026
Other versions4 projects use a version of this.
Word for word · 0
None found.
Edited · 0
None found.
Wrote their own version · 4
- wanshuiyin/Anti-Autoresearch★ 180same name
- 45ck/hci-review-skill★ 17same name
- Sunnyshinnny776/pm-agentic-cookbook★ 2same name
- igorkravcenko/snowshoe★ 1same 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 repository4 other files it gives its agents.
The file
We split this skill into the rules it gives an agent
12 rules. 0 are common, 10 are distinctive, and 2 are very specific to this project.
0
Common
Most of the 3 edited versions we read keep these.
10
Distinctive
This author's own choices. Worth a look.
2
Very specific
Tied to their project's names, files or tools. Probably skip.
No licence file, so all rights are reserved — read it at the source. We count its rules but don't quote them. Read them on GitHub.
“Common” is measured: kept by at least 6 in 10 of the 3 edited versions of this file we could read. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
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.