agentleFS
Sign inStart free
imMamdouhaboammarimMamdouhaboammar/get-things-done/.claude/skills/explore-codebase/SKILL.md

explore-codebase

Skill2 starsChanged 2 months agoMITView on GitHub

Navigate and understand codebase structure using the knowledge graph

13 other projects use a version of this, 2 of them edited.

Adopted by

Most recently taken up by

Used with

Projects with it also use incident-triage, explain-code and 2 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.
  • testified-ossSkill

    incident-triage

    Triage production incidents with severity assessment, root cause hypothesis, impact analysis, and escalation recommendations. Use when analyzing outages, errors, or production issues.

    Also in 3 projects that use this

  • zbruhnkeSkill

    explain-code

    Explain how code works in detail. Use when trying to understand unfamiliar code, complex logic, or system architecture.

    Also in 3 projects that use this

  • SentrySkill

    write-tests

    Write tests following project conventions. Use when adding new tests or modifying existing ones.

    Also in 3 projects that use this

  • GoogleSkill

    code-review

    Adversarial systems, concurrency, memory-model, and architecture code review protocol. Use this skill whenever asked to review code, PRs, diffs, or branches in Filament.

    Also in 3 projects that use this

The file

Show its rules and text

We split this skill into the rules it gives an agent

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

  • 0

    Common

    Most of the 11 edited versions we read keep these.

  • 3

    Distinctive

    This author's own choices. Worth a look.

  • 10

    Very specific

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

  • Common
  • Distinctive
  • Very specific
  1. Distinctive:

    Use the code-review-graph MCP tools to explore and understand the codebase.

    line 8
  2. Very specific:

    Run list_graph_stats_tool to see overall codebase metrics.

    line 12
  3. Very specific:

    Run get_architecture_overview_tool for high-level community structure.

    line 13
  4. Very specific:

    Use list_communities_tool to find major modules, then get_community_tool for details.

    line 14
  5. Very specific:

    Use semantic_search_nodes_tool to find specific functions or classes.

    line 15
  6. Very specific:

    Use query_graph_tool with patterns like callers_of, callees_of, imports_of to trace relationships.

    line 16
  7. Very specific:

    Use list_flows_tool and get_flow_tool to understand execution paths.

    line 17
  8. Distinctive:

    Start broad (stats, architecture) then narrow down to specific areas.

    line 21
  9. Very specific:

    Use children_of on a file to see all its functions and classes.

    line 22
  10. Very specific:

    Use find_large_functions_tool to identify complex code.

    line 23
  11. Very specific:

    Start with get_minimal_context_tool(task="<your task>") before other graph tools.

    line 26
  12. Very specific:

    Use detail_level="minimal" on all calls.

    line 27
  13. Distinctive:

    Read the implementation and its tests before changing code.

    line 29

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

Explore Codebase

Use the code-review-graph MCP tools to explore and understand the codebase.

Steps

  1. Run list_graph_stats_tool to see overall codebase metrics.
  2. Run get_architecture_overview_tool for high-level community structure.
  3. Use list_communities_tool to find major modules, then get_community_tool for details.
  4. Use semantic_search_nodes_tool to find specific functions or classes.
  5. Use query_graph_tool with patterns like callers_of, callees_of, imports_of to trace relationships.
  6. Use list_flows_tool and get_flow_tool to understand execution paths.

Tips

  • Start broad (stats, architecture) then narrow down to specific areas.
  • Use children_of on a file to see all its functions and classes.
  • Use find_large_functions_tool to identify complex code.

Token Efficiency Rules

  • Start with get_minimal_context_tool(task="<your task>") before other graph tools.
  • Use detail_level="minimal" on all calls. Only escalate to "standard" when minimal is insufficient.
  • Target: complete any review/debug/refactor task in ≤5 tool calls and ≤800 total output tokens.
  • Read the implementation and its tests before changing code. The graph narrows scope; it does not replace the source.

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