pr-review

Review PR Comments

Context

• Branch: !git branch --show-current
• Remote: !gh repo view --json nameWithOwner -q .nameWithOwner

Review conventions

Read .github/review.md before classifying comments. It defines blocking vs non-blocking prefixes and the expected comment format.

Task

Given PR number $ARGUMENTS (required), fetch and triage all reviewer comments.

1. Fetch comments

Run these two gh api calls to get both comment types:

# Inline review comments (attached to specific lines)
gh api repos/{owner}/{repo}/pulls/{pr}/comments --paginate

# Issue-level comments (general discussion)
gh api repos/{owner}/{repo}/issues/{pr}/comments --paginate

If --repo is provided in arguments, use that. Otherwise infer from the git remote.

Filter out bot comments (author login ending in [bot] or bot).

2. Parse and classify

For each human comment, extract:

• Author: .user.login
• Type: review (inline) or discussion (issue-level)
• File + line: .path and .line (review comments only)
• Body: .body
• Prefix: match the first word against .github/review.md prefix semantics
• Blocking: true if prefix is blocking:, must-fix:, bug:, security:, or tests:
• Created: .created_at

3. Summarize

Output a table grouped by blocking status:

## Blocking (must resolve before merge)

| # | Author | File:Line | Comment |
|---|--------|-----------|---------|
| 1 | anny   | main.tf:159 | concern about subnet tag collision across envs |

## Non-blocking (address or acknowledge)

| # | Author | File:Line | Comment |
|---|--------|-----------|---------|
| 1 | anny   | hooks.py:37 | (tagged Windsor re: except clause syntax) |

For comments without a prefix, classify as non-blocking per review.md default.

4. Suggest next steps

For each blocking comment, suggest the minimal fix. If the comment is a question, draft a reply. If it requires a code change, identify the file and describe what to change.