Graph Guided Code Reading

Save tokens by reading the codebase as a dependency graph, not as a pile of files.

Core Principle

Most repo-reading waste comes from opening too many files too early. Build a small relevance graph first, then read only the nodes that matter.

Minimal Relevance Graph

For each task, identify only:

• the user-visible entrypoint or changed surface;
• the owning module or service;
• the direct dependencies and dependents that shape behavior;
• the nearest tests, config, or contracts that constrain the change.

Stop expanding once the next action is clear.