codebase-analysis
Skill0 starsChanged 8 months agoNo licenceView on GitHub
Techniques for analyzing existing codebases to reverse-engineer requirements and understand business logic. Use when conducting brownfield analysis or understanding existing system capabilities. Adapts to repo size. Supports iterative refinement via doc= argument. Ends with a review loop then an output gate — never writes to project memory without user confirmation.
7 other projects use a version of this.
Adopted by
Most recently taken up by
- mahdy-gribkov/arcanatheir own version, first seen Nov 8, 2026
- medy-gribkov/arcanatheir own version, first seen Nov 1, 2026
- ArduPilot/MethodicConfiguratortheir own version, first seen Oct 8, 2026
- tony-adamson/groundworktheir own version, first seen Jul 15, 2026
- ptsilivis/autonomousguytheir own version, first seen Jul 4, 2026
- enzowyf/codebase-analysistheir own version, first seen Apr 10, 2026
Other versions7 projects use a version of this.
Word for word · 0
None found.
Edited · 0
None found.
Wrote their own version · 7
- ArduPilot/MethodicConfigurator★ 173same name
- Ycsyyds/codebase-analysis-skill★ 34same name
- ptsilivis/autonomousguy★ 33same name
- tony-adamson/groundwork★ 4same name
- mahdy-gribkov/arcana★ 1same name
- medy-gribkov/arcana★ 1same name
- enzowyf/codebase-analysis★ 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 repository3 other files it gives its agents.
- architecture-documentSkill
- architecture-reviewerSkill
- memory-maintainerSkill
The file
Show its rules and text
We split this skill into the rules it gives an agent
48 rules. 0 are common, 34 are distinctive, and 14 are very specific to this project.
0
Common
Most of the 7 edited versions we read keep these.
34
Distinctive
This author's own choices. Worth a look.
14
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 7 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.
Reviews can't be read right now.
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.