review-pr

Analyze merge-base diffs to verify PR changes align with stated goals.

34|71|Updated Jan 27, 2026
One-click install
npx skills add https://github.com/hw-native-sys/simpler --skill review-pr-hw-native-sys
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: review-pr
Source: https://github.com/hw-native-sys/simpler/tree/main/.claude/skills/review-pr
Command: npx skills add https://github.com/hw-native-sys/simpler --skill review-pr-hw-native-sys

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

PR review workflows often grapple with misalignments between the stated goals in a PR and the actual changes introduced. This Skill analyzes the correct merge-base diff (base to HEAD) to reconcile the PR body's intended goals with what the changes actually implement, surfacing gaps, contradictions, and risks early in the review process.

Core Features & Use Cases

  • Compare merge-base diffs to verify that PR changes realize stated objectives and flag discrepancies.
  • Extract user-stated goals from input and cross-check against commit messages, PR body, and linked issues or design docs.
  • Provide structured review outputs including goal alignment, risk signals, and suggested next steps; optionally run independent reviews from local codex/gemini CLIs when opted-in.

Quick Start

Ask me to review a PR by its number or branch and I will compare the merge-base diff to HEAD and summarize goals, gaps, and risk.

Frequently Asked Questions about review-pr

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I verify that pull request changes align with their stated goals?

To verify pull request changes align with stated goals, analyze the merge-base diff to HEAD. This process extracts user-stated objectives and cross-checks them against actual commits, surfacing gaps, contradictions, and risk signals early.

What is a merge-base diff and why is it needed for code review?

A merge-base diff compares the base branch to HEAD, isolating only the changes introduced by a pull request. It is needed for accurate code review to ensure the analysis reflects actual modifications rather than unrelated upstream commits.

Can I integrate external CLI reviewers like codex or gemini into my PR review?

Yes, you can integrate external reviewers like codex or gemini into your PR review. When explicitly requested, the review process can optionally run independent analyses using these local CLIs alongside the standard goal verification.

How do I review a branch by its number or name to find discrepancies?

To review a branch by its number or name, provide the identifier and the tool will compare the merge-base diff to HEAD. It then summarizes the stated goals, identifies implementation gaps, and signals potential risks.

Does PR review automation work without external dependencies or components?

Yes, PR review automation works without external dependencies or components. It natively analyzes git diffs and commit messages to provide structured outputs including goal alignment and next steps directly.

What are the limitations of automated goal extraction in pull request reviews?

Automated goal extraction relies on the clarity of input from the PR body, commit messages, and linked issues. Limitations arise when these sources are vague, contradictory, or missing, which may hinder accurate alignment verification.