StackMap
Subscribe

code-review-graph vs Understand-Anything

Local-first code intelligence graph for AI coding tools: Tree-sitter AST graph + blast-radius analysis served over MCP, so agents read ~82x fewer tokens per review question. — versus — Plugin for Claude Code and 16 other hosts that turns any codebase into an interactive knowledge graph — multi-agent analysis, layered dashboard, guided tours, diff-impact view, domain mapping.

The curated verdict

Code knowledge graphs for opposite consumers: understand-anything renders an explorable dashboard to teach humans the architecture; code-review-graph feeds minimal context to agents.

code-review-graphUnderstand-Anything
Stars21k75k
Forks2.1k6.2k
LanguagePythonTypeScript
LicenseMITMIT
Last activityyesterday4 days ago
Topicscodingcoding
Curated connections44

code-review-graph — the curator's take

The rare benchmark-honest repo: it tells you the 528x number is the best case and its recall metric is circular. Install once, it configures 14 platforms (Codex, Claude Code, Cursor...). Reach for it on monorepos where review context is the token sink; skip on small repos where a grep costs less than the graph's own metadata.

Understand-Anything — the curator's take

The onboarding killer app, and its motto is the right one: graphs that teach, not graphs that impress. /understand runs a multi-agent pipeline over the repo, then the dashboard gives you architecture layers, dependency-ordered guided tours, semantic search, diff blast-radius, and a business-domain view that maps code to real processes. The team trick is the sleeper: the graph is plain JSON — commit it once and every teammate skips the analysis. Incremental re-runs + a post-commit auto-update hook keep it fresh. Budget real tokens for the first full run on a large repo (their own warning), or point it at a local model. NOT an agent context server — this graph is for humans first; when you want a code graph served TO agents over MCP, that's codegraph-mcp or tokensave territory.