review-pr
Review a PR or branch diff using the knowledge graph for full structural context. Outputs a structured review with blast-radius analysis.
Install
npx skills add https://github.com/tirth8205/code-review-graph --skill review-prSKILL.md
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.
Related skills
improve-codebase-architecturemattpocock1MScan a codebase for deepening opportunities, present them as a visual HTML report, then grill through whichever one you pick.codebase-designmattpocock691KShared vocabulary for designing deep modules. Use when the user wants to design or improve a module's interface, find deepening opportunities, decide where a seam goes, make code more testable or AI-navigable, or when another skill needs the deep-module vocabulary.web-design-guidelinesvercel-labs676KReview UI code for Web Interface Guidelines compliance. Use when asked to "review my UI", "check accessibility", "audit design", "review UX", or "check my site against best practices".code-reviewmattpocock631KReview the changes since a fixed point (commit, branch, tag, or merge-base) along two axes: Standards (does the code follow this repo's documented coding standards?) and Spec (does the code match what the originating issue/spec asked for?). Runs both reviews in parallel sub-agents and reports them side by side. Use when the user wants to review a branch, a PR, work-in-progress changes, or asks to \"review since X\".
