codegraphlisted

# CodeGraph CodeGraph indexes a repository into a local symbol/call graph and answers structural questions through MCP tools or the `codegraph` CLI. Use a few narrow graph queries to find what matters, then read only that source. Graph evidence narrows the search; source is the final authority. ## First moves - Vague or task-level request → `context_for_task` with the task text. - Known symbol name → `find_symbol`. - "Who uses this?" / "What does this use?" → `find_callers` / `find_callees`. - Planning a risky or broad change → read `references/change-impact.md`. - Empty, ambiguous, or surprising result → read `references/trust.md`. ## Default workflow 1. **Orient.** `context_for_task(task=...)` returns ranked files and symbols with identities (`symbol_id`, `qualified_name`) — never source. If the response sets `has_more`, follow `next_cursor` only when the first page was not enough. If it returns nothing useful, rephrase once with concrete names from the task, then fall back to `find_symbol`/`search_symbols` — and to ordinary source search if the graph keeps coming up empty. 2. **Identify.** Pick the few symbols that actually matter from that page. 3. **Drill down.** `find_symbol` with `detail=excerpt` (or `full`) for that small set only. 4. **Relationships.** `find_callers` / `find_callees` before changing a load-bearing symbol. 5. **Blast radius** when the change is broad: impact, dependency, and test tools — see `references/change-impact.md`.