Review a PR or branch diff using the knowledge graph for full structural context. Outputs a structured review with blast-radius analysis.
Perform a comprehensive code review of a pull request or branch diff using the knowledge graph.
Token optimization: Before starting, call get_docs_section_tool(section_name="review-pr") for the optimized workflow. Never include full files unless explicitly asked.
Identify the changes for the PR:
git diff main...<branch> to get changed filesUpdate the graph by calling build_or_update_graph_tool(base="main") to ensure the graph reflects the current state.
Get the full review context by calling get_review_context_tool(base="main"):
main (or the specified base branch) as the diff baseAnalyze impact by calling get_impact_radius_tool(base="main"):
Deep-dive each changed file:
query_graph_tool(pattern="callers_of", target=<func>) for high-risk functionsquery_graph_tool(pattern="tests_for", target=<func>) to verify test coverageGenerate structured review output:
## PR Review: <title>
### Summary
<1-3 sentence overview>
### Risk Assessment
- **Overall risk**: Low / Medium / High
- **Blast radius**: X files, Y functions impacted
- **Test coverage**: N changed functions covered / M total
### File-by-File Review
#### <file_path>
- Changes: <description>
- Impact: <who depends on this>
- Issues: <bugs, style, concerns>
### Missing Tests
- <function_name> in <file> - no test coverage found
### Recommendations
1. <actionable suggestion>
2. <actionable suggestion>
semantic_search_nodes_tool to find related code the PR might have missed