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
- Call
health_checkand record the active profile and tool count. Stop with an installation or configuration instruction if the server is unavailable. - Resolve the repository root to an absolute path. Choose a task-scoped, absolute, writable
output_dirfor graph artifacts; never use the source root or a broad system directory as that output. - Call
analyze_codebasewith the repository path and output directory. Reuse the exactgraph_pathreturned by the tool in every later call. - Immediately call
query_graphwithgraph="missed". Treat parse-incomplete, skipped, and quarantined files as explicit coverage gaps. Absence from this report is not proof of complete indexing. - Use
search_codebaseto discover qualified symbol names. Drill into relevant hits withget_contextorget_symbol; do not guess qualified names. - Use read-only
query_graphqueries for structural questions the typed tools do not answer. AddORDER BYbefore paging withnext_offset. - 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.