github-pr-review

Reviews GitHub pull requests adversarially and squash-merges them after verification.

1|1|Updated Aug 2, 2026
One-click install
npx skills add https://github.com/blac9216/waypoint --skill github-pr-review-blac9216
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: github-pr-review
Source: https://github.com/blac9216/waypoint/tree/main/.claude/skills/github-pr-review
Command: npx skills add https://github.com/blac9216/waypoint --skill github-pr-review-blac9216

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve? Pull requests authored by an AI agent need an independent reviewer that does not trust the author's claims, and teams need a consistent, evidence-based gate before code lands on the main branch. ## Core Features & Use Cases - Contextless adversarial review: A fresh reviewer agent reads only the PR, linked issue, and diff, then works a ten-point attack list covering spec fidelity, silent failures, concurrency, security, and style-guide rules. - Full verification pipeline: Checks CI status, runs unit and integration tests, enforces coverage thresholds (80% or no regression), scans for secrets, and walks the PR's suggested test steps. - Structured verdicts and merge: Posts Changes Requested, Decomposition Requested, Approved, or Escalation comment templates, files deferred issues for non-blocking findings, and squash-merges only after a clean review. - Use Case: After an agent opens a PR closing issue #42, dispatch this skill in a subagent to independently verify the fix, run the test suite, request changes on findings, and squash-merge once the review is clean. ## Quick Start Ask the agent to review pull request number 42 using the github-pr-review skill and merge it only if the review comes back clean.

Frequently Asked Questions about github-pr-review

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

FAQPage Schema
How do I review a GitHub pull request with an AI agent?▼

Dispatch this skill with the PR number in a fresh subagent. It reads the PR, linked issue, and diff, runs tests and coverage checks, then posts a structured verdict comment and squash-merges only if the review is clean.

How does the skill verify a PR actually fixes the linked issue?▼

It extracts the linked issue from the PR body, reads every acceptance criterion, and marks each as met, unmet, or pending-live. Any unmet requirement becomes a blocker finding that prevents merging.

Does the review work in both local and cloud sandbox environments?▼

Yes. Locally it uses the gh CLI for PR reads, diffs, checks, and merges. In the cloud sandbox it uses GitHub MCP tools such as pull_request_read, get_job_logs, and merge_pull_request with equivalent operations.

What happens when a pull request is too large to review?▼

If the diff exceeds roughly 400 net lines or 15 files, the skill posts a Decomposition Requested template instead of reviewing. The author must split the work into smaller PRs, and the attempt counts as a review round.

Why does the review stop after three rounds?▼

Three rounds of Changes Requested without a clean PR indicate a problem automation cannot resolve. The skill posts an Escalation template, applies the help label to the PR and issue, and hands control to a human.

How are secrets in a pull request handled during review?▼

Any secret scanning hit is a blocker requiring three fixes: remove the secret from the diff, rewrite git history with filter-repo and force-push, and rotate the credential at the issuing system. The next round verifies all three.