code-structure
Skill1 starsChanged 2 days agoLicence not identifiedView on GitHub
Read-only review of the code structure of a whole repo (tree, manifests, import graph, entrypoints, docs, ADRs and git history), not line by line. Looks for module or layer boundaries that are not respected, dependency cycles, the same problem solved several ways, god-modules, files across modules that always change together, unused code and packages, and docs or ADRs that contradict the code. Ships deterministic scripts for the import graph (TS/JS, Python, Go) and the history. Reports and stops. Use it for "review the code structure", "find circular dependencies", "find dead code", "are module boundaries respected", "does this module do too much?", "what always changes together", even if they never say "structure". Not for system design (architecture-review), infra (infra-review) or line-by-line bugs (correctness-review and the others). Also triggers on Spanish requests such as "revisa la estructura del código", "¿hay dependencias circulares?", "¿qué código está muerto?" or "¿se respetan las capas?".
- Reads credentials
17 other projects use a version of this.
Adopted by
Most recently taken up by
- NemesLaszlo/claude-code-harnesstheir own version, first seen Nov 8, 2026
- kellykampen/agent-skillstheir own version, first seen Nov 1, 2026
- vijaysuperpositionist/skillstheir own version, first seen Nov 1, 2026
- michaelshimeles/rstacktheir own version, first seen Nov 1, 2026
- jars-demo/jars-skillstheir own version, first seen Oct 25, 2026
- Rajveerx11/skillstheir own version, first seen Oct 25, 2026
Other versions17 projects use a version of this.
Word for word · 0
None found.
Edited · 0
None found.
Wrote their own version · 17
- michaelshimeles/rstack★ 1.4ksame name
- michaelshimeles/skills★ 1.4ksame name
- The-Utopia-Studio/skills★ 6same name
- Spardutti/claude-skills★ 3same name
- jaydubya818/MissionControl★ 2same name
- kellykampen/agent-skills★ 2same name
- nitikeshq/skills★ 2same name
- rikvanriel/code-hygiene★ 2same name
- voundbrand/overnight★ 2same name
- Nagacash/nagacodex-factory-skill★ 1same name
7 more not listed
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 repository10 other files it gives its agents.
- api-security-reviewSkill
- apply-remediationSkill
- architecture-reviewSkill
- correctness-reviewSkill
- data-consistencySkill
- implicit-state-machinesSkill
- infra-reviewSkill
- llm-app-reviewSkill
- perf-diagnosisSkill
- repo-audit-swarmSkill
The file
We split this skill into the rules it gives an agent
4 rules. 0 are common, 2 are distinctive, and 2 are very specific to this project.
0
Common
Most of the 17 edited versions we read keep these.
2
Distinctive
This author's own choices. Worth a look.
2
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 17 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.