PR Multi-Perspective Review

When to Use

• Before merging any significant PR — to catch issues a single reviewer might miss
• When the PR touches multiple concerns (UI + API + infra all at once)
• For PRs with external impact: public API changes, auth logic, billing flows
• As a pre-merge gate in high-stakes or regulated environments

Differentiation from code-review: code-review is a single technical pass. This skill runs 6 distinct lenses simultaneously, surfacing business, quality, and operational issues that a developer reviewer alone would not flag.

Prerequisites

• PR is open and has a diff available (via gh CLI or GitHub MCP)
• At minimum: PR description exists (even if brief)

Workflow