pr-review

Reviews green pull requests on correctness and spec compliance, posting inline findings.

1|1|Updated Oct 3, 2021
One-click install
npx skills add https://github.com/benjr70/Smart-Smoker-V2 --skill pr-review-benjr70
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: pr-review
Source: https://github.com/benjr70/Smart-Smoker-V2/tree/main/.claude/skills/pr-review
Command: npx skills add https://github.com/benjr70/Smart-Smoker-V2 --skill pr-review-benjr70

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Autonomous coding agents open pull requests that still need a rigorous review before a human merges them. This Skill performs a one-time, two-axis review of a freshly green agent PR — checking both code correctness and fidelity to the issue's Acceptance Criteria — and routes the findings into an automated fix loop so no finding is lost. ## Core Features & Use Cases - Dual-axis review: Runs a correctness pass (via the built-in /code-review at medium effort) and a spec pass (diff vs. Acceptance Criteria and parent Spec) in parallel subagents. - Inline review comments: Posts deduplicated, severity-ranked findings as marked inline review threads on the PR, capped at 10 comments. - Automated fix handoff: Applies the AFK:revise label so the next daemon fire routes the PR into the /pr-reconcile loop, which fixes, replies, and resolves each thread. - Idempotency and safety: A done-marker comment guarantees the review runs exactly once per PR; the skill never commits, merges, or resolves threads itself. - Use Case: After an agent's PR passes CI, invoke this Skill to get a structured review posted on the PR and fixes queued automatically, keeping merge decisions human-gated. ## Quick Start Run /pr-review with the PR number, branch, and issue number to review the open agent pull request and post its findings.

Frequently Asked Questions about pr-review

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

FAQPage Schema
How do I run an automated code review on a GitHub pull request?

Invoke /pr-review with the PR number, branch, and issue number after CI passes. It runs a correctness pass and a spec-compliance pass in parallel, then posts findings as inline review comments on the PR.

How does the review check a PR against issue acceptance criteria?

The spec-axis reviewer extracts the Acceptance Criteria block and parent Spec from the issue, then compares the diff against them for missing requirements, scope creep, and spec mismatches, anchoring each finding to a diff line.

Does this skill fix the review findings it posts?

No. It only posts inline comments and applies the AFK:revise label. The /pr-reconcile loop owns all fixes, in-thread replies, and thread resolution on the next daemon fire.

Can the review run twice on the same pull request?

No. A done-marker comment acts as an idempotency gate checked before every run, and a duplicate guard skips findings that already have open threads at the same path and line.

What happens when inline comment posting fails on a diff line?

On a 422 error the posting retries once at the first added line of that file's first hunk. If that also fails, the finding is folded into the done-marker comment under a Could not anchor list.