code-intelligence

# code-intelligence > For a **structure** question — *who calls X*, *where is Y used*, *what > imports Z*, *what breaks if I change this symbol* — ask an index that already > exists before rebuilding the relationship by hand: it is already built, its > answer is structured, and it costs a fraction of the tokens. It is **not** more > precise than a blind `grep` — measured on this repository's own source, zero > classes met the win bar (§ Measured twice) — so grep is the arm you fall back > to routinely and **with a stated reason**, not grudgingly. This skill routes > such questions to the native code-graph engine (ADR-124, Class A) or a > consumer-shipped index first. It is the executable side of > [`external-code-graph-interop`](../../rules/external-code-graph-interop.md): > *orchestrator first, owner where it wins*. ## When to use - The question is about **relationships between code symbols**, not content: callers/callees, references, imports, inheritance, change-impact. - You are about to `grep`/`Read` across many files to reconstruct a call or import graph by hand. **When NOT to use:** content/semantic questions ("what does this function *mean*", "find the string 'password'"), single-file edits, or a repo with no code-graph and no appetite to build one — plain `grep`/read is right there. ## Procedure 1. **Detect the source.** `agent-config code-graph detect` — is a fresh consumer `graph.json` or native cache present? (A consumer-shipped fresh index wins; th...