// Review PR comments from GitHub. Fetches inline review comments and issue comments, classifies by blocking vs non-blocking, and summarizes actionable items.
| name | pr-review |
| description | Review PR comments from GitHub. Fetches inline review comments and issue comments, classifies by blocking vs non-blocking, and summarizes actionable items. |
| allowed-tools | Bash(gh *), Read, Grep, Glob, Agent |
| argument-hint | <pr-number> [--repo owner/repo] |
git branch --show-currentgh repo view --json nameWithOwner -q .nameWithOwnerGiven PR number $ARGUMENTS (required), fetch and triage all reviewer 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).
For each human comment, extract:
.user.loginreview (inline) or discussion (issue-level).path and .line (review comments only).bodyblocking:, must-fix:, bug:, security:, or tests: prefix.created_atOutput a table grouped by blocking status:
## Blocking (must resolve before merge)
| # | Author | File:Line | Comment |
|---|--------|-----------|---------|
| 1 | user | main.py:42 | concern about race condition |
## Non-blocking (address or acknowledge)
| # | Author | File:Line | Comment |
|---|--------|-----------|---------|
| 1 | user | utils.py:10 | nit: rename variable |
Comments without a blocking prefix are classified as non-blocking.
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.
Create a pull request using the wingman PR template. Injects git state, commit history, and diff stats automatically.
Create a changelog-style promotion PR between two branches. Use for release promotions or branch-to-branch merges with a structured changelog.
Design engineering principles for making TUI interfaces feel polished. Use when building Textual widgets, reviewing TUI code, implementing transitions, focus states, alignment, spacing, or any visual detail work. Triggers on TUI polish, design details, "make it feel better", "feels off", layout alignment, color consistency, responsive sizing.
Create a git commit with conventional commit format. Injects current git state automatically.
Explain system behavior, request flows, architecture, or implementation logic as short 4chan-style greentext lines. Use when the user asks for a step-by-step explanation, says "explain the logic", asks for "greentext", or wants terse sequential reasoning with each line starting with `>`.
Create a GitHub issue using the wingman issue templates (bug, feature). Injects branch and commit context automatically.