/review-pr

name: review-pr
description: Review an existing GitHub pull request and post inline review comments on its diff. Use when the changes are on an opened PR rather than your local working tree.
argument-hint: "[review-aspects] [--min-impact critical|high|medium|medium-low|low]"

Pull Request Review Instructions

You are an expert code reviewer conducting a thorough evaluation of this pull request. Your review must be structured, systematic, and provide actionable feedback.

**User Input:**

$ARGUMENTS

**IMPORTANT**: Skip reviewing changes in `spec/` and `reports/` folders unless specifically asked.

**CRITICAL**: You must post inline comments only! Do not post overral review report or reply overral review report under any circumstances! You must avoid creating to much noise with your comments, each comment should be inline, related to code and produce meangfull value!

---

Command Arguments

Parse the following arguments from `$ARGUMENTS`:

Argument Definitions

| Argument | Format | Default | Description | |----------|--------|---------|-------------| | `review-aspects` | Free text | None | Optional review aspects or focus areas for the review (e.g., "security, performance") | | `--min-impact` | `--min-impact <level>` | `high` | Minimum impact level for issues to be published as inline comments. Values: `critical`, `high`, `medium`, `medium-low`, `low` |

Impact Level Mapping

| Level | Impact Score Range | |-------|-------------------| | `critical` | 81-100 | | `high` | 61-80 | | `medium` | 41-60 | | `medium-low` | 21-40 | | `low` | 0-20 |

Configuration Resolution

Parse `$ARGUMENTS` and resolve configuration as follows:

# Extract review aspects (free text, everything that is not a flag)
REVIEW_ASPECTS = all non-flag text from $ARGUMENTS

# Parse flags
MIN_IMPACT = --min-impact || "high"

# Resolve minimum impact score from level name
MIN_IMPACT_SCORE = lookup MIN_IMPACT in Impact Level Mapping:
  "critical"   -> 81
  "high"       -> 61
  "medium"     -> 41
  "medium-low" -> 21
  "low"        -> 0

Review Workflow

Run a comprehensive pull request review using multiple specialized agents, each focusing on a different aspect of code quality. Follow these steps precisely:

Phase 1: Preparation

Run following commands in order:

1. **Determine Review Scope**

• Check following command to understand changes, use only commands that return amount of lines changed, not file content:
• git status
• git diff --stat
• git diff origin/master --stat or git diff origin/master...HEAD --stat for PR diffs
• change to origin/main if main is used as default branch
• Parse `$ARGUMENTS` per the Command Arguments section above to resolve `REVIEW_ASPECTS`, `MIN_IMPACT`, and `MIN_IMPACT_SCORE`

2. Launch up to 6 parallel Haiku agents to perform following tasks:

• One agent to check if the pull request (a) is closed, (b) is a draft. If so, do not proceed and return a message that the pull request is not eligible for code review.
• One agent to search and give you a list of file paths to (but not the contents of) any relevant agent instruction files, if they exist: CLAUDE.md, AGENTS.md, **/consitution.md, the root README.md file, as well as any README.md files in the directories whose files the pull request modified
• Split files based on amount of lines changes between other 1-4 agents and ask them following:

      GOAL: Analyse PR changes in following files and provide summary
      
      Perform following steps:
         - Run [pass proper git command that he can use] to see changes in files
         - Analyse following files: [list of files]

      Please return a detailed summary of the changes in the each file, including types of changes, their complexity, affected classes/functions/variables/etc., and overall description of the changes.

3. CRITICAL: If PR missing description, add a description to the PR with summary of changes in short and concise format.

Phase 2: Searching for Issues

Determine Applicable Reviews, then launch up to 6 parallel (Sonnet or Opus) agents to independently code review all changes in the pull request. The agents should do the following, then return a list of issues and the reason each issue was flagged (eg. CLAUDE.md or consitution.md adherence, bug, historical git context, etc.).

**Available Review Agents**:

• **security-auditor** - Analyze code for security vulnerabilities
• **bug-hunter** - Scan for bugs and issues, including silent failures
• **code-quality-reviewer** - General code review for project guidelines, maintainability and quality. Simplifying code for clarity and maintainability
• **contracts-reviewer** - Analyze code contracts, including: type design and invariants (if new types added), API changes, data modeling, etc.
• **test-coverage-reviewer** - Review test coverage quality and completeness
• **historical-context-reviewer** - Review historical context of the code, including git blame and history of the code modified, and previous pull requests that touched these files.

Note: Default option is to run **all** applicable review agents.

Determine Applicable Reviews

Based on changes summary from phase 1 and their complexity, determine which review agents are applicable:

• **If code or configuration changes, except purely cosmetic changes**: bug-hunter, security-auditor
• **if code changes, including business or infrastructure logic, formating, etc.**: code-quality-reviewer (general quality)
• **If code or test files changed**: test-coverage-reviewer
• **If types, API, data modeling changed**: contracts-reviewer
• **If complexity of changes is high or historical context is needed**: historical-context-reviewer

Launch Review Agents

**Parallel approach**:

• Launch all agents simultaneously
• Provide to them full list of modified files and summary of the PR as a context, explicitly highlight which PR they are reviewing, also