review-pr
Review a PR or branch diff using the knowledge graph for full structural context. Outputs a structured review with blast-radius analysis.
- 1,149
- installs
- 0 up / 0 down, score 0.00
- votes
- 32,264
- repo stars
- Updated
- less than a month ago
- In the catalog since
- 6 Oct 2026
- From
- tirth8205/code-review-graph
Skill instructions
Rendered from the published SKILL.md, 43 lines.
Review PR
Review all commits of a pull request or branch against its base branch.
Steps
- Identify the changes. With a branch name run
git diff --name-only main...<branch>; otherwise diff the current branch againstmain(ormaster). Use that ref asbasebelow. - Call
get_minimal_context_tool(task="review PR", base="main"). If it returnsstatus: not_ready, callbuild_or_update_graph_tool()and continue. - Call
detect_changes_tool(base="main", detail_level="minimal")for risk-scored changed functions, test gaps and affected flows across the whole branch. - For high-risk functions call
query_graph_tool(pattern="callers_of", target="<function>")andquery_graph_tool(pattern="tests_for", target="<function>"). Flag public API changes whose callers were not updated. - Call
get_review_context_tool(base="main")for source snippets, orget_impact_radius_tool(base="main")for the full dependent list, only when step 3 leaves a high-risk item unclear. - Read the changed source of the highest-impact files first. Do not load whole files unless the change needs it.
Output
## 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>
Tips
- Use
semantic_search_nodes_toolto find related code the PR may have missed.