pr-reviewer

PR Reviewer

Overview

This skill reviews pull requests in hyperswitch-prism with a strict, evidence-driven, code-only posture. It uses a nested-subagent workflow:

orchestrator -> classifier -> scenario subagents -> aggregator

Each PR is classified into one or more of 13 repo-specific scenarios, then reviewed by the exact specialist subagents that match. The review covers changed files, required companion files, and produces a structured verdict with blocking/non-blocking findings.

When to Use

• User asks to review a PR (by URL, number, or diff)
• User asks to review all open GRACE PRs in batch
• User asks to re-review a PR after author updates
• User asks to review a PR raised by 10xGRACE

Workflows

Choose the workflow based on the request:

To execute a review: Read the selected workflow file and follow it exactly. Use nested subagents if the tool supports them; otherwise emulate the same phases serially.

Quick Start

Full review by PR URL

Review PR https://github.com/juspay/hyperswitch-prism/pull/123.
Read grace/rulesbook/pr-reviewer/workflows/full-pr-review.md and follow it exactly.
Use nested subagents if the tool supports them; otherwise emulate the same phases serially.

Review a PR raised by 10xGRACE

Review PR #123 in hyperswitch-prism.
This PR was raised by 10xGRACE / GRACE automation.
Read grace/rulesbook/pr-reviewer/workflows/grace-pr-review.md and follow it exactly.
Use nested subagents if the tool supports them; otherwise emulate the same phases serially.

Batch review all open GRACE PRs

Review all open GRACE PRs in hyperswitch-prism.
Read grace/rulesbook/pr-reviewer/workflows/batch-grace-pr-review.md and follow it exactly.
Use nested subagents if the tool supports them; otherwise emulate the same phases serially.

Incremental review after updates

Re-review PR #123 in hyperswitch-prism after the latest commits.
Read grace/rulesbook/pr-reviewer/workflows/incremental-review.md and follow it exactly.
Use nested subagents if the tool supports them; otherwise emulate the same phases serially.

Review System Architecture

Phase 0 -- Load Configuration

Read these files before any review:

• grace/rulesbook/pr-reviewer/README.md -- system overview and principles
• grace/rulesbook/pr-reviewer/config/path-rules.yaml -- scenario taxonomy, path triggers, companion files
• grace/rulesbook/pr-reviewer/config/rubric.yaml -- severity levels, decision rules, scenario checklists
• grace/rulesbook/pr-reviewer/config/output-template.md -- required output structure
• grace/rulesbook/pr-reviewer/prompts/orchestrator.md -- top-level controller

Phase 1 -- Classify

Run grace/rulesbook/pr-reviewer/prompts/classifier.md to determine:

• Primary and secondary scenarios
• Metadata scenarios (e.g., grace-generated-pr)
• Subagents and reviewer families to dispatch
• Companion files to check

Phase 2 -- Review

Spawn one subagent per matched scenario from grace/rulesbook/pr-reviewer/subagents/. Fall back to family reviewers in grace/rulesbook/pr-reviewer/reviewers/ if no dedicated subagent exists.

Phase 3 -- Aggregate

Run grace/rulesbook/pr-reviewer/prompts/aggregator.md to deduplicate findings, normalize severities, and produce the final verdict using grace/rulesbook/pr-reviewer/config/output-template.md.

Scenario Coverage

Reviewer Families

Core Principles

• Read every changed file fully -- never approve from title, summary, or snippets
• Classify first, then review with matching scenario specialists
• Keep comments anchored to code and required companion files only
• Escalate mixed PRs instead of flattening into one generic review
• Fail closed when safety cannot be verified from evidence

Reference Index