Review a PR or branch diff using the knowledge graph for full structural context. Outputs a structured review with blast-radius analysis.
75%
Does it follow best practices?
Run evals on this skill
Adds up to 20 points to the overall score
Passed
No findings from the security scan
Fix and improve this skill with Tessl
tessl review fix ./skills/review-pr/SKILL.mdReview 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.tirth8205/code-review-graph
115dccf
If you maintain this skill, you can claim it as your own. Once claimed, you can manage eval scenarios, bundle related skills, attach documentation or rules, and ensure cross-agent compatibility.