Review all changes in a pull request or branch against its base branch. Use a knowledge graph, a map of code relationships, to report affected files and functions, test coverage, API compatibility issues, and recommended actions.
Review a PR or branch diff using the knowledge graph for full structural context. Outputs a structured review with blast-radius analysis.
Review the instructions the agent will receive before you install.
Review all commits of a pull request or branch against its base branch.
git diff --name-only main...<branch>; otherwise diff the current branch against main (or master). Use that ref as base below.get_minimal_context_tool(task="review PR", base="main"). If it returns status: not_ready, call build_or_update_graph_tool() and continue.detect_changes_tool(base="main", detail_level="minimal") for risk-scored changed functions, test gaps and affected flows across the whole branch.query_graph_tool(pattern="callers_of", target="<function>") and query_graph_tool(pattern="tests_for", target="<function>"). Flag public API changes whose callers were not updated.get_review_context_tool(base="main") for source snippets, or get_impact_radius_tool(base="main") for the full dependent list, only when step 3 leaves a high-risk item unclear.## PR Review: <title>
### Summary
<1-3 sentences>
### Risk
- Overall: Low / Medium / High
- Blast radius: <n> files, <m> functions
- Test coverage: <covered> of <changed> changed functions
### Files
#### <path>
- Changes: <what>
- Impact: <who depends on it>
- Issues: <bugs, style, concerns>
### Missing Tests
- <function> in <file>
### Recommendations
1. <action>
semantic_search_nodes_tool to find related code the PR may have missed.No reviews yet. Tell others what you thought.
No login needed. Share how it worked for you, ask a question, or note where it did not run.
No comments yet. Be the first to write one.
Build or refresh a knowledge graph, a map of code relationships used for code review. Choose a full rebuild or an incremental update, then report the operation's status and summary.
Investigate bugs using a graph of code relationships. Find relevant functions, trace calls and execution paths, check recent changes, and assess what a proposed fix could affect before reading and changing the implementation.
Explore an unfamiliar codebase using a graph of code relationships. Inspect its structure, find functions and classes, trace calls and imports, follow execution paths, and locate large functions for closer investigation.
Plan refactoring with dependency analysis, which shows how code parts rely on each other. Find candidates and unreferenced code, preview and apply renames, and compare the resulting impact with the original plan.
Review code changes using a knowledge graph, a map of code relationships, to assess risk and affected behavior. Organize findings by severity, identify missing tests, suggest fixes, and provide a merge recommendation.
Review code changes against the previous commit and identify affected files and functions. Use dependency relationships to assess risk, check missing tests, and produce a focused report with issues and recommendations.