review-pr

Reviews GitHub pull requests with inline comments and formal approve or request-changes verdicts.

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

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) and references (resource) components.

What problem does it solve? Manual pull request review is inconsistent: reviewers miss re-review context, post comments on invalid diff lines, duplicate prior findings, and skip formal verdicts. This Skill enforces a structured GitHub PR review workflow that detects re-reviews, calibrates strictness, and posts findings correctly via the GitHub API. ## Core Features & Use Cases - Re-review detection: Fetches prior reviews, commits, and comment threads to categorize findings as addressed, still open, or new — avoiding duplicate comments. - Strictness modes: Recommends Quick, Standard, Thorough, or Strict mode based on PR size and security sensitivity (auth, RBAC, CI/CD changes), confirmed with the user before analysis. - Inline comments plus formal verdict: Posts each finding as a separate 🔴/🟡/🟢 inline comment verified against diff hunks, then submits a separate APPROVE or REQUEST_CHANGES review with linked findings. - Batch and large-PR support: Reviews multiple PRs in parallel with subagents and falls back to paginated file APIs when diffs exceed GitHub's size limits. - Use Case: Run /review-pr https://github.com/org/repo/pull/123 to get a deep analysis with inline blocker comments and a formal REQUEST_CHANGES verdict, or re-review a PR after fixes to confirm prior blockers are resolved. ## Quick Start Ask the assistant to review a GitHub pull request by providing its URL or number, for example: review PR https://github.com/org/repo/pull/123 and post inline comments with a formal verdict.

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 GitHub pull request with inline comments?▼

Provide the PR URL or number, and the skill fetches the diff, runs deep analysis, and posts each finding as a separate inline comment via the GitHub API. It then submits a formal APPROVE or REQUEST_CHANGES review as a separate call.

How does re-review detection work for previously reviewed PRs?▼

The skill fetches your prior reviews via the pulls/reviews API, then compares commits and comment threads since that review. Findings are categorized as addressed, still open, or new, and resolved threads get a reply instead of a duplicate comment.

Can I review multiple pull requests at once?▼

Yes, batch mode accepts multiple PR URLs or numbers and spawns one parallel analysis subagent per PR. Results are consolidated into a single summary table before one confirmation to post all findings.

Why do inline PR comments fail with 422 errors?▼

GitHub rejects comments on lines outside the diff hunks. The skill prevents this by computing new-file line numbers from @@ hunk headers and verifying every target line against hunk ranges before posting.

What happens when a PR diff is too large for gh pr diff?▼

For PRs over roughly 300 files, gh pr diff returns HTTP 406. The skill falls back to the paginated pulls/files API or a shallow clone with git diff to stage the full diff for analysis.

When should I use Strict mode versus Quick mode for PR review?▼

Strict mode is recommended for security-sensitive changes like auth, RBAC, or CI/CD workflows, and requests changes even for concerns. Quick mode suits hotfixes and small config tweaks, approving unless definite blockers exist.