skills.rest
SgtPooki
SgtPookiCOMMUNITY
Explore all skills by this author →
Website𝕏@SgtPookiGitHub

review-pr

Reviews pull requests against code standards and originating specs with optional GitHub draft delivery.

1|Updated Mar 24, 2026
Search Tags:#code review#pull request#github#gh cli#review comments#spec conformance#standards gate
One-click install
npx skills add https://github.com/SgtPooki/skills --skill review-pr-sgtpooki
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: review-pr
Source: https://github.com/SgtPooki/skills/tree/main/skills/review-pr
Command: npx skills add https://github.com/SgtPooki/skills --skill review-pr-sgtpooki

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Reviewing a pull request requires checking both code quality and whether the diff actually implements what the originating issue or spec asked for, and doing both consistently is tedious and error-prone. ## Core Features & Use Cases - Standards gate: Delegates the standards sweep to code-standards-review in gate mode, reusing its severity model and report contract. - Spec conformance axis: Locates the originating issue or spec from PR references, user-supplied paths, or docs, then flags missing requirements, wrong implementations, and scope creep. - Pending GitHub review delivery: On request, posts findings as a PENDING GitHub review with inline diff-anchored comments that the user publishes manually. - Use Case: A teammate opens a PR claiming to close issue #45; run this skill to verify the diff meets the issue's requirements, catch unrequested changes, and leave a draft review with inline comments. ## Quick Start Ask the agent to review pull request number 123 against its linked issue and post the findings as a pending GitHub review.

Frequently Asked Questions about review-pr

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

FAQPage Schema
How do I review a pull request against its original issue or spec?▼

Resolve the PR, then trace issue references in the PR body and commit messages to fetch the originating spec. Compare the diff against each requirement and report missing, wrong, or out-of-scope changes with quoted spec lines as evidence.

How to post code review findings as a draft GitHub review?▼

Create a pending review via the GitHub API by omitting the event field, which keeps it visible only to you until published. Each inline comment needs a path, line, and side anchored to a diff hunk; unanchorable findings go in the review body.

What is the difference between review-pr and code-standards-review?▼

code-standards-review runs a standards check on any diff without needing a PR or spec. review-pr layers on top of it, adding spec conformance analysis against the originating issue and optional delivery as a pending GitHub review.

Why does GitHub reject inline review comments on some lines?▼

GitHub only accepts comments anchored to lines within diff hunks. Validate each comment's path and line against the actual hunks first; anything outside the diff must go into the review body instead.

Can I have multiple pending reviews on the same pull request?▼

No, GitHub allows only one pending review per user per PR. If one already exists, stop and inform the user rather than deleting or overwriting it.

Related Skills

Explore More Software Engineering Skills→
FradSerFradSer
588

code-review

Reviews a git diff against coding standards and the originating spec using parallel sub-agents.

Community
Advanced
badbsallyybadbsallyy

prepare-pr

Rebase a GitHub pull request onto main and run automated checks.

Community
Advanced
fancivefancive

cr

Coordinate cross-model code reviews between Claude and Codex with structured P1/P2/P3 reports.

Community
Advanced
mattpocockmattpocock
242.8k

code-review

Reviews a git diff against repo coding standards and the originating spec using parallel sub-agents.

Community
Intermediate