Address PR review feedback by systematically working through every unresolved PR review thread on the current branch's PR - analyze each comment, make the requested code changes (with tests where useful), commit, and optionally reply and resolve.
gh extension list | grep -q pr-review || gh extension install agynio/gh-pr-review
gh pr-review subcommand requires both --pr <number> and --repo <owner/repo> — do not omit either. Look the values up once at the start of the workflow and substitute the literal numbers and slugs into every later command.gh pr view --json number -q .number
gh repo view --json nameWithOwner -q .nameWithOwner
--pr 42 --repo posit-dev/skills — on every subsequent gh pr-review call in this workflow (review view, comments reply, threads resolve, etc.).gh pr-review review view --pr <number> --repo <owner/repo>
--reviewer <login> — Filter by specific reviewer--states <list> — Comma-separated review states (APPROVED, CHANGES_REQUESTED, COMMENTED, DISMISSED)--unresolved — Show only unresolved threads--tail <n> — Show only the last n replies per thread--include-comment-node-id — Include GraphQL node IDs for repliesgh pr-review comments reply --thread-id <PRRT_...> --body "<reply-text>" --repo <owner/repo> --pr <number>
--body "$(cat <<'EOF' ... EOF\n)" heredoc syntax.gh pr-review threads resolve --thread-id <PRRT_...> --pr <number> --repo <owner/repo>
PRRT_...) come from review view --include-comment-node-id.