parallel-pr-review

Reviews batches of GitHub pull requests by fanning out parallel review subagents and synthesizing verdicts.

12.6k|1.5k|Updated Feb 3, 2026
One-click install
npx skills add https://github.com/nearai/ironclaw --skill parallel-pr-review
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: parallel-pr-review
Source: https://github.com/nearai/ironclaw/tree/main/docs/internal/archived-skills/parallel-pr-review
Command: npx skills add https://github.com/nearai/ironclaw --skill parallel-pr-review

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Reviewing many open pull requests one by one exhausts context and produces shallow, inconsistent feedback, especially with stacked branches, merge conflicts, or security-sensitive changes.

Core Features & Use Cases

  • Parallel fan-out review: Spawns one read-only review subagent per PR or per stack, each producing a structured verdict (APPROVE / APPROVE WITH NITS / REQUEST CHANGES) with severity-tagged findings.
  • Tailored rubrics: Applies a fixed review rubric covering correctness, security, privacy/logging, test non-vacuity, and structural maintainability, with adversarial angles customized per PR.
  • Cross-PR synthesis and posting: Aggregates verdicts into a summary table, identifies recurring bug classes and landing order, and posts review comments via the GitHub CLI only when requested.
  • Use Case: A maintainer returns to a repository with 15 open PRs including a stacked series and a conflicting branch; the skill triages them, reviews each in parallel, and delivers a consolidated report of what to land first.

Quick Start

Ask the assistant to review the open PRs in the current repository using the gh CLI.

Frequently Asked Questions about parallel-pr-review

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

FAQPage Schema
How do I review multiple open pull requests at once on GitHub?

List open PRs with gh pr list, group standalone PRs and stacked series, then fan out one review subagent per PR or stack in parallel. Each agent runs gh pr diff, applies a fixed rubric, and returns a verdict that gets synthesized into a cross-PR summary.

How to review stacked pull requests that depend on each other?

Assign one agent per stack and have it review each PR's own gh pr diff in dependency order, noting the merge order. Detect stacked PRs by checking whether the base branch is something other than main.

What tools are required to run a batch PR review workflow?

The workflow requires the GitHub CLI (gh) for listing PRs, fetching diffs, and posting review comments, plus git for branch inspection and cleanup of fetched review branches after the pass completes.

When should I not use parallel PR review?

Skip it for a single PR, which you can review directly, and for a PR you authored mid-task, where normal self-review applies. The fan-out approach is designed for batches, stacks, or recurring review passes.

Why does gh pr list show a PR as conflicting when it is actually clean?

The mergeable status can be stale because conflicts sometimes clear after an upstream rebase. Re-check the PR before flagging it, and have the review agent diagnose the actual cause with git fetch and git log.

Should automated reviews post formal approvals on other people's PRs?

No. Default to review comments via gh pr review --comment, which carries the verdict in the body without flipping GitHub's merge-blocking state. Only post formal approve or request-changes when explicitly asked.