graft

Run graft callers with the symbol name to get precomputed call and reference edges rather than a text search. Use --depth 2 for the usual blast radius or --depth all before a refactor to map every connected file.

Run graft map for a token-budgeted tour of directory clusters, hub files, and global hotspots from the wiring graph. Then read the hub cards it names instead of skeletoning or asking through every subsystem.

graft ask returns ranked top-N hits for conceptual or locational questions and can miss instances. graft grep exhaustively finds every occurrence of a pattern grouped by enclosing symbol, so use it when you need all call sites.

No. Every graft command runs locally at zero cost, needs no API key, and returns in under a second. The graph refreshes itself before each query, so results always reflect current uncommitted edits.

An over-specific regex like a full signature returns nothing even when the code is indexed. Loosen the pattern to the bare symbol name and retry graft grep rather than switching to raw grep -rn, which is slower and unranked.

Read source only when a span is truncated, a node lacks a needed detail, or files are genuinely not indexed such as docs and brand-new files. Even then, open the exact file:line range graft names rather than whole files.