GEMINI.md

1<!-- code-review-graph MCP tools -->
2## MCP Tools: code-review-graph
3 
4**IMPORTANT: This project has a knowledge graph. ALWAYS use the
5code-review-graph MCP tools BEFORE using Grep/Glob/Read to explore
6the codebase.** The graph is faster, cheaper (fewer tokens), and gives
7you structural context (callers, dependents, test coverage) that file
8scanning cannot.
9 
10### When to use graph tools FIRST
11 
12- **Exploring code**: `semantic_search_nodes_tool` or `query_graph_tool` instead of Grep
13- **Understanding impact**: `get_impact_radius_tool` instead of manually tracing imports
14- **Code review**: `detect_changes_tool` + `get_review_context_tool` instead of reading entire files
15- **Finding relationships**: `query_graph_tool` with callers_of/callees_of/imports_of/tests_for
16- **Architecture questions**: `get_architecture_overview_tool` + `list_communities_tool`
17 
18Fall back to Grep/Glob/Read **only** when the graph doesn't cover what you need.
19 
20### Key Tools
21 
22| Tool | Use when |
23|------|----------|
24| `detect_changes_tool` | Reviewing code changes — gives risk-scored analysis |
25| `get_review_context_tool` | Need source snippets for review — token-efficient |
26| `get_impact_radius_tool` | Understanding blast radius of a change |
27| `get_affected_flows_tool` | Finding which execution paths are impacted |
28| `query_graph_tool` | Tracing callers, callees, imports, tests, dependencies |
29| `semantic_search_nodes_tool` | Finding functions/classes by name or keyword |
30| `get_architecture_overview_tool` | Understanding high-level codebase structure |
31| `refactor_tool` | Planning renames, finding dead code |
32 
33### Workflow
34 
351. The graph auto-updates on file changes (via hooks).
362. Use `detect_changes_tool` for code review.
373. Use `get_affected_flows_tool` to understand impact.
384. Use `query_graph_tool` pattern="tests_for" to check coverage.
39