code-review-graphlisted

# Code Review Graph — Token-Efficient Codebase Context via MCP > Cut AI token usage substantially on large codebases by giving the AI a structural map instead of letting it read everything. Savings scale with codebase size — marginal on small projects, large on monorepos. ## Overview `code-review-graph` is an MCP server that uses **Tree-sitter** to parse your codebase into an AST graph stored in **SQLite**. When your AI assistant needs context for a task, it queries the graph first — getting only the files in the **blast radius** of your change — instead of reading every file in the directory. **Token Impact (illustrative — varies by codebase):** | Codebase Type | Pattern | |---------------|---------| | Large monorepo (10K+ files) | Biggest savings — graph reads a small fraction of files | | Mid-size app (1-5K files) | Meaningful reduction on multi-file changes | | Small project (<200 files) | Little benefit — graph overhead can exceed savings | > **Quality angle:** scoping the AI to the blast radius reduces noise, which tends to improve review focus. Measure on your own repo rather than relying on a fixed multiplier. ## Bootstrap Protocol (opt-in) When invoked during `/plan` or standard usage on a mid-to-large project, check whether graph analysis is available before relying on it: 1. **Step 1:** Check if the tool is installed: `Get-Command code-review-graph` (Windows) or `which code-review-graph` (macOS/Linux). 2. **Step 2:** Check if a `.code-review-graph/` directo