agentleFS
Sign inStart free
cdeustcdeust/ai-architect-mcp-codebase/skills/understand-codebase/SKILL.md

understand-codebase

Skill7 starsChanged 3 months agoMITView on GitHub

Build an evidence-backed map of an unfamiliar repository with the ai-architect code graph. Use before implementing a feature, debugging an unfamiliar subsystem, explaining architecture, or making structural claims about symbols and dependencies.

2 other projects use a version of this.

Adopted by

Most recently taken up by

  • Other versions2 projects use a version of this.

    Word for word · 0

    None found.

    Edited · 0

    None found.

    Wrote their own version · 2

    1. kimtth/agent-skill-100-lines-or-less★ 2same name
    2. cordanaLLM/praetor★ 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.

The file

We split this skill into the rules it gives an agent

6 rules. About 0 are common, 0 are distinctive, and 6 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.

  • 6

    Very specific

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

  • Common
  • Distinctive
  • Very specific
  1. Very specific:

    Use the eight-tool core profile.

    line 8
  2. Very specific:

    If a full-profile workflow supplies a check_security_gates receipt, inspect both gates_passed and assessment_complete.

    line 17
  3. Very specific:

    Call health_check and record the active profile and tool count.

    line 24
  4. Very specific:

    Call analyze_codebase with the repository path and output directory.

    line 26
  5. Very specific:

    Use search_codebase to discover qualified symbol names.

    line 28
  6. Very specific:

    Use read-only query_graph queries for structural questions the typed tools do not answer.

    line 29

≈ “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.

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

Understand Codebase

Use the eight-tool core profile. Do not assume that pipeline-only tools are available.

For Rust caller or impact questions, request lsp: true in analyze_codebase and make rust-analyzer available. Inspect lsp_status.state: disabled means static-only analysis; failed means analysis continued and may retain partial LSP results. Record the error and treat affected conclusions as unverified until source checks or a successful rerun support them. completed means the pass returned, not that every call resolved. Record unresolved sites and coverage gaps.

If a full-profile workflow supplies a check_security_gates receipt, inspect both gates_passed and assessment_complete. A true pass with an incomplete assessment is not security clearance: report skipped checks, unresolved symbols and warnings. This core-profile workflow does not invoke that additional tool.

Workflow

  1. Call health_check and record the active profile and tool count. Stop with an installation or configuration instruction if the server is unavailable.
  2. Resolve the repository root to an absolute path. Choose a task-scoped, absolute, writable output_dir for graph artifacts; never use the source root or a broad system directory as that output.
  3. Call analyze_codebase with the repository path and output directory. Reuse the exact graph_path returned by the tool in every later call.
  4. Immediately call query_graph with graph="missed". Treat parse-incomplete, skipped, and quarantined files as explicit coverage gaps. Absence from this report is not proof of complete indexing.
  5. Use search_codebase to discover qualified symbol names. Drill into relevant hits with get_context or get_symbol; do not guess qualified names.
  6. Use read-only query_graph queries for structural questions the typed tools do not answer. Add ORDER BY before paging with next_offset.
  7. For any important negative result, inspect the coverage report and use targeted source search for the relevant symbols and call forms, including unflagged files, before concluding that a symbol or edge does not exist. A clean coverage report does not establish relationship completeness.

Deliverable

Return a compact map of entry points, components, important symbols, dependencies, and available call-graph paths. Tie every structural claim to a tool result. Label interpretations as inferences and list uncovered files or unresolved references as limitations.

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