agentleFS
future-minefuture-mine/claude-skill/skills/codebase-cartographer/SKILL.md

codebase-cartographer

Skill1 starsChanged 35 days agoNo licenceView on GitHub

Explore an existing, old, or undocumented codebase and produce a recovered `.product/` foundation that reflects how the system ACTUALLY works. Use this whenever the user has inherited, joined, or needs to safely change a legacy / production / unfamiliar repository and says things like "help me understand this codebase", "I inherited this app and the docs are missing", "map out how this system works", "reverse-engineer the architecture", "what does this legacy service actually do", or "I need to work on a production system I didn't write". It reads truth from the code as-is — real architecture, tech stack, dependency graph, data flows, and an honest RISK_MAP of fragile / undocumented / high-blast-radius areas, INCLUDING accidental behavior — and seeds a KNOWN_ISSUES log. Everything else in the legacy-intervention suite reads these recovered docs. Use this, NOT product-architect, when the system already exists; product-architect is for designing a NEW product from a fresh idea.

  • Commits and pushes

2 other projects use a version of this.

Adopted by

Most recently taken up by

The file

We split this skill into the rules it gives an agent

3 rules. About 0 are common, 0 are distinctive, and 3 are very specific to this project.

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈0

    Distinctive · estimate

    This author's own choices. Worth a look.

  • 3

    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 an estimate: at least 1 in 5 of the 350,495 skill files we read have a rule of the same kind, not the same words. “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
What did you use it for? e.g. Reviewing pull requests in a Rails app

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.