repo-graph

# Guides

How to install repo-graph and use it in real coding workflows. Short, practical, copy-paste.

Start here

### Install repo-graph in any AI client

A 60-second setup that gives your AI coding assistant a structural map of any codebase. Exact command per client, plus how to confirm it loaded.

### Your AI assistant reads too much. Give it a map.

AI coding assistants grep and read across a repo before they answer. A structural map lets the model read only what matters. Proof in the numbers.

Workflows

### Trace a frontend action to its backend handler

Follow a feature across the stack with repo-graph trace, flow, and find instead of grepping both sides and guessing the link.

### Know what breaks before you change it

See the downstream blast radius of a change before editing, grouped by tier, using repo-graph's impact and neighbours tools.

### Understand a new repo before you touch it

Onboard to an unfamiliar codebase without reading every file. Use repo-graph's status, dense_text, flow, and graph_view to orient and drill in.

### Find where a feature lives, fast

Locate a feature's cluster of code from a couple of seed terms using repo-graph's find and activate, then flow to see it end to end.

### Make your AI assistant navigate by structure

Teach Claude Code, Cursor, and Codex to call status before grepping, scope with the right repo-graph tool, and trust the graph.