agentleFS
Sign inStart free
JordanCoinJordanCoin/codemap/.claude/skills/explore/SKILL.md

explore

Skill710 starsChanged 8 months agoMITView on GitHub

Systematic codebase exploration using codemap's analysis tools. Use when understanding how code works, tracing dependencies, or onboarding to a new area.

67 other projects use a version of this.

Adopted by

Most recently taken up by

Used with

Projects with it also use agent-context-isolation, agentica-infrastructure and 10 more.

Other files people use alongside this one.

Files found in the same public projects as a version of this one, more often than they turn up anywhere else. Each project counts once, large collections count for less, and this file's own repository is left out.

The file

We split this skill into the rules it gives an agent

3 rules. 0 are common, 2 are distinctive, and 1 is very specific to this project.

  • 0

    Common

    Most of the 58 edited versions we read keep these.

  • 2

    Distinctive

    This author's own choices. Worth a look.

  • 1

    Very specific

    Tied to their project's names, files or tools. Probably skip.

  • Common
  • Distinctive
  • Very specific
  1. Distinctive:

    Read hub files in the chain first: they define the shared types/interfaces

    line 19
  2. Very specific:

    Check .codemap/config.json for routing subsystems: they define logical boundaries

    line 23
  3. Distinctive:

    Read the subsystem's docs first, then trace the code

    line 25

“Common” is measured: kept by at least 6 in 10 of the 58 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.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
SKILL.md

Systematic Codebase Exploration

Start with the big picture

  1. codemap .: project tree with file counts and top extensions
  2. codemap --deps .: dependency flow showing how packages connect
  3. Hub files: these are the most important files to understand first

Trace a feature

  1. Find the entry point (CLI command, API route, event handler)
  2. codemap --importers <entry-file>: who calls this?
  3. codemap --deps .: follow the import chain
  4. Read hub files in the chain first: they define the shared types/interfaces

Understand a subsystem

  1. Check .codemap/config.json for routing subsystems: they define logical boundaries
  2. Each subsystem has paths, keywords, and associated docs
  3. Read the subsystem's docs first, then trace the code

Find what you're looking for

QuestionCommand
Where is X defined?codemap find "<words from its name>"
Where is this bug?codemap find "<symptom words>" scores names first, then body text ((body) hits); grep for the exact symptom text
Who uses X?codemap --importers <file>
What's the architecture?codemap --deps . → look at hub files
What changed recently?codemap --diff
What was I working on?Check working set in prompt-submit output

Download now (ZIP)

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.

Check your setup, free