review-pr

Review Pull Request

Review code changes in a specific pull request using a comprehensive multi-agent code review process with specialized reviewers for architecture, code quality, and test coverage.

Usage

/review-pr <PR_NUMBER>

Examples:

• /review-pr 123 - Review pull request #123
• /review-pr 45 - Review pull request #45

Instructions

You are coordinating a comprehensive code review for pull request #$ARGUMENTS.

Step 1: Gather PR Information

First, collect information about the pull request:

1. Get PR details, changed files, and the HEAD commit SHA:

   if [ -z "$ARGUMENTS" ]; then
     echo "Error: Missing PR number. Usage: /review-pr <PR_NUMBER>" >&2
     exit 1
   fi
   
   if ! printf '%s\n' "$ARGUMENTS" | grep -Eq '^[0-9]+$'; then
     echo "Error: Invalid PR number '$ARGUMENTS'. PR number must be a positive integer. Usage: /review-pr <PR_NUMBER>" >&2
     exit 1
   fi
   
   gh pr view "$ARGUMENTS" --json number,title,body,baseRefName,headRefName,headRefOid,url,files
   gh pr diff "$ARGUMENTS"
   

2. Extract key information:

   • List of changed files
   • PR URL for linking in review comments
   • HEAD commit SHA (headRefOid) - required for posting inline comments

3. IMPORTANT: Save the diff output - you will need it to:

   • Include relevant diff context snippets in each finding
   • Determine the exact target file line numbers for inline comments (absolute line numbers in the target file, computed from the diff hunk headers, as required by /post-review-comments)
   • Determine the side (RIGHT for additions +, LEFT for deletions -)

4. Create the .codereviews/ directory if it doesn't exist.

Step 2: Launch Parallel Code Reviews

Launch THREE sub-agents in parallel using the Task tool. Each agent MUST receive:

• The PR number: $ARGUMENTS
• The list of changed files (so they stay scoped to PR files only)
• The PR URL for generating clickable links

CRITICAL: You MUST launch all three agents in a SINGLE message with THREE parallel Task tool calls: