cartographer
Skill0 starsChanged 5 months agoLicence not identifiedView on GitHub
Build and maintain a persistent codemap (.codemap/*.json — structure, dependencies, functions, warnings) of any codebase. Function-level extraction runs in four stages — tags, spec_refs, qualified names + git blame default-on; call graph opt-in. Use whenever the user asks to build, refresh, or rebuild the codemap; to map the code; to find duplicate, stale, or unused files; to ask "what's impacted if I change X" (forward/backward impact analysis over the call graph, spec sections joined in); or as part of an audit (app-audit Phase 0.5). Incremental refresh after the first full build. Works on any language.
9 other projects use a version of this.
Adopted by
Most recently taken up by
- apattichis/agentic-research-toolkittheir own version, first seen Nov 8, 2026
- luci-efe/skillstheir own version, first seen Nov 1, 2026
- Lexideck-Technologies/Lexideck2026their own version, first seen Oct 25, 2026
- dsvid/claude-skillstheir own version, first seen Oct 8, 2026
- qduc/claude-skillstheir own version, first seen Jul 26, 2026
- stevederico/cartographertheir own version, first seen Jul 18, 2026
Other versions9 projects use a version of this.
Word for word · 0
None found.
Edited · 0
None found.
Wrote their own version · 9
- mark-quinn/rosetta★ 9same name
- Lexideck-Technologies/Lexideck2026★ 2same name
- utxo-AG/claude-skills★ 2same name
- apattichis/agentic-research-toolkit★ 1same name
- spinchange/cartographer-skill★ 1same name
- stevederico/cartographer★ 1same name
- dsvid/claude-skills★ 0same name
- luci-efe/skills★ 0same name
- qduc/claude-skills★ 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 repository4 other files it gives its agents.
- app-auditSkill
- audit-fixSkill
- pre-commit-verificationSkill
- spec-bootstrapSkill
The file
Show its rules and text
We split this skill into the rules it gives an agent
15 rules. 0 are common, 11 are distinctive, and 4 are very specific to this project.
0
Common
Most of the 8 edited versions we read keep these.
11
Distinctive
This author's own choices. Worth a look.
4
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 8 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.