ak-review-pr

name	ak:review-pr
description	Review a GitHub pull request thoroughly — analyze diff for correctness, security, breaking changes, code quality, and AI-slop patterns. Supports --fix to auto-remediate findings and --reply to post the review back to GitHub via the gh CLI as a formal review.
user-invocable	true
when_to_use	Invoke to review a GitHub PR by number/URL, optionally fix findings, optionally post the review back to GitHub.
category	utilities
keywords	["pr","pull request","review","github","gh","fix","reply","anti-slop","ai-slop"]
argument-hint	<PR number or URL> [--fix] [--reply]
allowed-tools	["Bash(gh pr view *)","Bash(gh pr diff *)","Bash(gh pr checks *)","Bash(gh pr review *)","Bash(gh pr comment *)","Bash(gh api *)","Bash(gh auth status *)","Bash(command *)","Bash(git log *)","Bash(git diff *)","Bash(git status *)","Bash(git branch *)","Bash(git rev-parse *)","Bash(git add *)","Bash(git commit *)","Bash(git push *)","Bash(date *)","Read","Edit","MultiEdit","Write","Glob","Grep","Task"]
metadata	{"author":"agentkit","version":"2.0.0"}

Review Pull Request

Review PR $ARGUMENTS in this repository.

Modes

• Review-only (default): review the PR and print findings to chat. Do not edit, commit, or push.
• Fix loop (--fix): review, fix all actionable findings, commit+push, then re-review. Repeat until no actionable findings remain.
• Reply (--reply): after the review (or after the fix loop converges), post the review back to the PR via gh pr review.

Flags compose: review-pr 123 --fix --reply runs the fix loop and posts the final re-review at the end. Flag order does not matter.

Argument parsing

Derive PR_REF from $ARGUMENTS by stripping --fix and --reply flags:

!`PR_REF="$(printf '%s' "$ARGUMENTS" | sed -E 's/(^|[[:space:]])(--fix|--reply)([[:space:]]|$)/ /g; s/^[[:space:]]+//; s/[[:space:]]+$//')" && printf 'PR_REF=%s\n' "$PR_REF"`

Detect flags (the substring match below is intentional — flags may appear in any order):

• --fix present → fix-loop mode active
• --reply present → reply mode active

Context

PR metadata:

!`PR_REF="$(printf '%s' "$ARGUMENTS" | sed -E 's/(^|[[:space:]])(--fix|--reply)([[:space:]]|$)/ /g; s/^[[:space:]]+//; s/[[:space:]]+$//')" && gh pr view "$PR_REF" --json title,body,author,baseRefName,headRefName,files,additions,deletions,changedFiles`

PR diff:

!`PR_REF="$(printf '%s' "$ARGUMENTS" | sed -E 's/(^|[[:space:]])(--fix|--reply)([[:space:]]|$)/ /g; s/^[[:space:]]+//; s/[[:space:]]+$//')" && gh pr diff "$PR_REF"`

CI check status:

!`PR_REF="$(printf '%s' "$ARGUMENTS" | sed -E 's/(^|[[:space:]])(--fix|--reply)([[:space:]]|$)/ /g; s/^[[:space:]]+//; s/[[:space:]]+$//')" && gh pr checks "$PR_REF" 2>/dev/null || echo "No checks found"`

Diff stat (use to gauge scope vs description claims):

!`PR_REF="$(printf '%s' "$ARGUMENTS" | sed -E 's/(^|[[:space:]])(--fix|--reply)([[:space:]]|$)/ /g; s/^[[:space:]]+//; s/[[:space:]]+$//')" && gh pr diff "$PR_REF" --name-only 2>/dev/null | head -50`

Instructions

Perform a thorough code review of this PR. Follow these steps:

1. Understand the PR

• Read the PR title, description, and linked issues