pr-review-help

Review GitHub pull requests for strategic merge readiness and leadership verdicts.

3|1|Updated Feb 28, 2026
One-click install
npx skills add https://github.com/auerbachb/claude-code-config --skill pr-review-help
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: pr-review-help
Source: https://github.com/auerbachb/claude-code-config/tree/main/.claude/skills/pr-review-help
Command: npx skills add https://github.com/auerbachb/claude-code-config --skill pr-review-help

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill provides a short, evidence-backed leadership review of one or more GitHub pull requests to decide whether to merge, gate behind a flag, split, or hold based on strategic fit and operational readiness.

Core Features & Use Cases

  • Strategic Verdicts: Produces a ship/flag/approve/discuss/hold recommendation from a CTO/CPO/Chief Data Scientist lens.
  • Evidence-Driven Analysis: Requires concrete references to diffs, PR discussion, linked issues, and repository context (OKRs or README/milestones) for every concern.
  • Parallel Portfolio Reviews: Spawns per-PR subagents to analyze multiple PRs in parallel and synthesizes a portfolio-level merge order and cross-PR themes.
  • Operational Guidance: Emits a copy-pasteable cleanup prompt for hands-on remediation and follow-up tasks when action is required.

Quick Start

Request an executive review by invoking the skill with one or more PR numbers like /pr-review-help #123 #456.

Frequently Asked Questions about pr-review-help

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

FAQPage Schema
How do I review GitHub pull requests for strategic fit and merge readiness?

To review multiple PRs for merge readiness, provide PR numbers to trigger parallel subagent analysis. The skill synthesizes portfolio-level merge ordering, identifies cross-PR themes, and generates strategic verdicts based on evidence from diffs and repository context.

What is an executive code review for leadership decisions?

Executive code review requires access to PR metadata, diffs, linked issues, review threads, and repository context such as OKRs or README milestones. Without these inputs, the skill cannot produce evidence-backed leadership verdicts or operational cleanup prompts.

Can I assess multiple GitHub pull requests in parallel for merge ordering?

Yes, parallel portfolio reviews spawn per-PR subagents to analyze multiple GitHub pull requests simultaneously. The synthesis produces a portfolio-level merge order and identifies cross-PR themes to guide strategic leadership decisions across the entire batch.

What repository context do I need for a strategic PR risk assessment?

Strategic PR risk assessment requires repository context including OKRs or README milestones, PR metadata, diffs, linked issues, and review threads. This context ensures leadership verdicts are evidence-backed and aligned with operational goals before merging.

How do I generate cleanup prompts for pull requests that need remediation?

When executive PR review identifies operational issues, it emits copy-pasteable cleanup prompts for hands-on remediation. These prompts guide developers with specific follow-up tasks required to achieve merge readiness based on the strategic assessment.