코드 검토 그래프: Claude Code 토큰 사용을 줄이는 영구 코드 그래프

Stop burning tokens. Start reviewing smarter. Claude Code re-reads your entire codebase on every task. code-review-graph fixes that. It builds a structural map of your code with Tree-sitter, tracks changes incrementally, and gives Claude precise context so it reads only what matters. pip install code-review-graph code-review-graph install # auto-detects and configures all supported platforms code-review-graph build # parse your codebase One command sets up everything. install detects which AI coding tools you have and writes the correct MCP configuration for each one. Restart your editor/tool after installing. To target a specific platform: code-review-graph install --platform cursor # configure only Cursor code-review-graph install --platform claude-code # configure only Claude Code Requires Python 3.10+ and uv. | Platform | Config file | Auto-detected | |---|---|---| | Claude Code | .mcp.json | Yes | | Cursor | .cursor/mcp.json | Yes | | Windsurf | .windsurf/mcp.json | Yes | | Zed | .zed/settings.json | Yes | | Continue | .continue/config.json | Yes | | OpenCode | .opencode/config.json | Yes | Then open your project and ask your AI assistant: Build the code review graph for this project The initial build takes ~10 seconds for a 500-file project. After that, the graph updates automatically on every file edit and git commit. Your repository is parsed into an AST with Tree-sitter, stored as a graph of nodes (functions, classes, imports) and edges (calls, inheritance, test coverage), then queried at review time to compute the minimal set of files Claude needs to read. Blast-radius analysis When a file changes, the graph traces every caller, dependent, and test that could be affected. This is the "blast radius" of the change. Claude reads only these files instead of scanning the whole project. Incremental updates in # Target a specific platform code-review-graph build # Parse entire codebase code-review-graph update # Incremental update (changed files only) code-review-graph status # Graph statistics code-review-graph watch # Auto-update on file changes code-review-graph visualize # Generate interactive HTML graph code-review-graph wiki # Generate markdown wiki from communities code-review-graph detect-changes # Risk-scored change impact analysis code-review-graph register # Register repo in multi-repo registry code-review-graph unregister # Remove repo from registry code-review-graph repos # List registered repositories code-review-graph eval # Run evaluation benchmarks code-review-graph serve # Start MCP server MCP tools Claude uses these automatically once the graph is built. | Tool | Description | |---|---| build_or_update_graph_tool | Build or incrementally update the graph | get_impact_radius_tool | Blast radius of changed files | get_review_context_tool | Token-optimised review context with structural summary | query_graph_tool | Callers, callees, tests, imports, inheritance queries | semantic_search_nodes_tool | Search code entities by name or meaning | embed_graph_tool | Compute vector embeddings for semantic search | list_graph_stats_tool | Graph size and health | get_docs_section_tool | Retrieve documentation sections | find_large_functions_tool | Find functions/classes exceeding a line-count threshold | list_flows_tool | List execution flows sorted by criticality | get_flow_tool | Get details of a single execution flow | get_affected_flows_tool | Find flows affected by changed files | list_communities_tool | List detected code communities | get_community_tool | Get details of a single community | get_architecture_overview_tool | Architecture overview from community structure | detect_changes_tool | Risk-scored change impact analysis for code review | refactor_tool | Rename preview, dead code detection, suggestions | apply_refactor_tool | Apply a previously previewed refactoring | generate_wiki_tool | Generate markdown wiki from communities | get_wiki_page_tool | Retrieve a specific wiki page | list_repos_tool | List registered repositories | cross_repo_search_tool | Search across all registered repositories | MCP Prompts (5 workflow templates): review_changes , architecture_map , debug_issue , onboard_developer , pre_merge_check | Feature | Details | |---|---| | Incremental updates | Re-parses only changed files. Subsequent updates complete in under 2 seconds. | | 18 languages | Python, TypeScript/TSX, JavaScript, Vue, Go, Rust, Java, Scala, C#, Ruby, Kotlin, Swift, PHP, Solidity, C/C++, Dart, R, Perl | | Blast-radius analysis | Shows exactly which functions, classes, and files are affected by any change | | Auto-update hooks | Graph updates on every file edit and git commit without manual intervention | | Semantic search | Optional vector embeddings via sentence-transformers, Google Gemini, or MiniMax | | Interactive visualisation | D3.js force-directed graph with edge-type toggles and search | | Local storage | SQLite file in .code-review-graph/ . No external database, no cloud dependency. | | Wa