mcpField
R
review-pr

review-pr

github.com/tirth8205Testing & quality32.5k1.2k installsUpdated 2w ago
Repository

About review-pr

A code-review skill for reviewing every commit in a pull request or branch against its base. It prioritizes risk-scored changes, affected callers, tests, and high-impact files.

Key features

  1. 01Risk-scored change detection
  2. 02Caller and test impact checks
  3. 03Targeted review context
  4. 04Review summary with risk and blast radius

Use cases

  1. 01Reviewing a branch before merging
  2. 02Checking public API changes for missed callers
  3. 03Identifying test gaps and affected flows

MCP support

Uses code-review-graph MCP tools to analyze changes, dependencies, tests, and affected flows.

Install

Copy the command and run it in a terminal.

$npx skills add https://github.com/tirth8205/code-review-graph --skill review-pr

After installing, type/review-prin Claude Code to confirm it loaded.

Details

From the project README

Review PR

Review all commits of a pull request or branch against its base branch.

Steps

  1. Identify the changes. With a branch name run git diff --name-only main...<branch>; otherwise diff the current branch against main (or master). Use that ref as base below.
  2. Call get_minimal_context_tool(task="review PR", base="main"). If it returns status: not_ready, call build_or_update_graph_tool() and continue.
  3. Call detect_changes_tool(base="main", detail_level="minimal") for risk-scored changed functions, test gaps and affected flows across the whole branch.
  4. For high-risk functions call 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.
  5. Call 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.
  6. 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_tool to find related code the PR may have missed.

Comments

Markdown supported