Explore Codebase

Use the codegraph index to understand the repository before editing.

Core Rules

Prefer the host's MCP tools when exposed (codegraph_explore, codegraph_node); otherwise the same output comes from the CLI (codegraph explore, codegraph node).
Prefer graph results for entry points, call paths, dependents, and impact; confirm anything load-bearing by reading the source it points at.
If the index is missing or stale, run $build-graph first. If codegraph is unavailable or empty, continue with rg, manifests, README files, and config inspection.

Build or sync the index if it is empty or stale ($build-graph).
codegraph files --format grouped for the module layout.
codegraph explore "<task or area>" for the relevant symbols' source plus call paths in one shot; codegraph context "<task>" for a task-shaped bundle.
codegraph node -f <file> --symbols-only for a file's symbols and who depends on it (hubs = files "used by" many others).
codegraph callers|callees <symbol> and codegraph impact <symbol> to narrow to specific symbols and risky chokepoints.