Fetching from the wire…
Public story · 2026-07-27 · high
The project's GitHub stars jumped by 4,577 in the week ending July 27, though its own benchmark shows precision from 44 to 79 percent.
Why now: The 4,577-star jump landed in the week ending July 27, right as the project's benchmark numbers started making the rounds.
code-review-graph builds a searchable graph of a repo's functions, classes and imports, then feeds AI agents only the files a question touches, per its GitHub page.
That matters for anyone paying per-token costs to run coding agents: the project's own benchmarks report a median 82x reduction in tokens per question across six test repos, ranging from 38x on the low end to 528x on the high end.
The tool works by parsing source into a Tree-sitter AST, then linking functions, classes and imports through call, inheritance and test-coverage edges. It stores that graph in SQLite under a .code-review-graph/ folder and exposes it as an MCP server, so an agent can query what calls a function instead of grepping the whole repo.
Language coverage is wide: 30+ languages plus Jupyter, Databricks and Ansible, with Vue and Svelte support, and custom languages can be added through a languages.toml file without forking the project.
Impact-accuracy F1 sits at 0.71, with precision ranging 0.44 to 0.79 depending on the repo. That's a wide enough spread that a graph query can hand an agent the wrong file for anywhere between one in five and one in two questions, depending on which codebase you point it at.
I run a homegrown version of this same idea, and the token savings are real, they drop API costs and speed up how fast an agent lands on a correct answer. But the precision range means I still keep grep in my back pocket for anything I don't want to get wrong. Watch whether precision holds above 0.7 as more people point this at messier, older codebases than the six it was benchmarked on.
Each link below shares sources, entities, or timing with this story.
Anthropic released MCP / Shared entities / Same source / Shared topic / Earlier coverage
Linked by a graph relationship (Anthropic released MCP); both cover MCP, Tree; cite the same source (This Python project).
Claude Code uses MCP / Shared entities / Same source / Earlier coverage
Linked by a graph relationship (Claude Code uses MCP); both cover AST, MCP, Tree; cite the same source (This Python project).
Claude uses MCP / Shared entities / Same source / Shared topic / Earlier coverage
Linked by a graph relationship (Claude uses MCP); both cover AST, Tree; cite the same source (This Python project).
Cursor uses MCP / Shared entities / Same source domain / Shared topic / Earlier coverage
Linked by a graph relationship (Cursor uses MCP); both cover SQLite, Tree; reported by the same outlet (github.com).
Claude Code uses MCP / Shared entities / Same source domain / Earlier coverage
Linked by a graph relationship (Claude Code uses MCP); both cover AST, MCP, Tree; reported by the same outlet (github.com).
Claude uses MCP / Shared entity: MCP / Same source domain / Shared topic / Earlier coverage / Tension
Linked by a graph relationship (Claude uses MCP); both cover MCP; reported by the same outlet (github.com).
Claude Code uses MCP / Shared entity: Databricks / Same source domain / Shared topic / Earlier coverage
Linked by a graph relationship (Claude Code uses MCP); both cover Databricks; reported by the same outlet (github.com).
Claude Code uses MCP / Shared entity: MCP / Same source domain / Shared topic / Earlier coverage
Linked by a graph relationship (Claude Code uses MCP); both cover MCP; reported by the same outlet (github.com).