code-analyzer
Skill2 starsChanged 4 months agoLicence not identifiedView on GitHub
Rigorous TWO-AXIS code reviewer. Standards - does the code follow THE PROJECT's rules guide (docs/sdd/09-review-rules.md)? Spec - did the code fulfill its originating spec/PRD (did it do what was asked)? The two are measured separately and reported side by side; a reproval is always anchored in a textual citation (a guide rule OR a spec line) - it never invents. Use when the user asks to review code, analyze conformity, do a code review, check whether the code follows the standards or fulfilled the spec, or when spec-create suggests a review at the end of a feature. Agnostic to architecture and language.
6 other projects use a version of this.
Adopted by
Most recently taken up by
- jerry-guo-mys/skillstheir own version, first seen Nov 8, 2026
- jablonkai/skillstheir own version, first seen Oct 1, 2026
- CharTyr/Mai-Skill-Loadertheir own version, first seen Jun 25, 2026
- zb-keen/skillstheir own version, first seen Apr 22, 2026
- orange4664/research-skillstheir own version, first seen Mar 31, 2026
- nimbalyst/skillstheir own version, first seen Feb 16, 2026
Other versions6 projects use a version of this.
Word for word · 0
None found.
Edited · 0
None found.
Wrote their own version · 6
- orange4664/research-skills★ 41same name
- nimbalyst/skills★ 28same name
- CharTyr/Mai-Skill-Loader★ 4same name
- jablonkai/skills★ 2same name
- jerry-guo-mys/skills★ 1same name
- zb-keen/skills★ 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 repository11 other files it gives its agents.
- adr-createSkill
- arch-cleanSkill
- arch-hexagonalSkill
- arch-layeredSkill
- arch-onionSkill
- diagnosing-bugsSkill
- evidence-captureSkill
- junit-cleanSkill
- spec-createSkill
- spec-executeSkill
- spec-initSkill
The file
We split this skill into the rules it gives an agent
5 rules. 0 are common, 2 are distinctive, and 3 are very specific to this project.
0
Common
Most of the 3 edited versions we read keep these.
2
Distinctive
This author's own choices. Worth a look.
3
Very specific
Tied to their project's names, files or tools. Probably skip.
The licence could not be identified — 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.