workflow-pr-review-followuplisted

# Workflow: PR Review Follow-up **Announce at start:** "I'm using the workflow-pr-review-followup skill to re-check PR #N." ## When to invoke - The user runs `/swe-workbench:review --check-followup <N>`. - A reviewer has already posted a full review and wants to verify that their findings were addressed. - Phrases: "re-check PR 123", "check if my review comments were addressed", "follow up on review #456". ## When NOT to invoke - Full first-pass review → use `swe-workbench:workflow-pr-review` instead. - The PR is closed/merged → out of scope. ## Composition This skill orchestrates; analysis is delegated to: - `swe-workbench:reviewer` subagent — produces `Severity | File:Line | Issue | Why | Fix` findings + a Review Decision footer. - `swe-workbench:ticket-context` skill — prepended when PR references a ticket key. ## 7-step flow ### Step 1 — Pre-flight ```bash gh auth status >/dev/null || { echo "gh not authenticated. Run 'gh auth login'."; exit 1; } CURRENT_USER=$(gh api /user -q .login) mkdir -p /tmp/swe-workbench-pr-review gh pr view "$PR" --json state,number,headRefName,baseRefName,headRefOid,title,body,author \ > "/tmp/swe-workbench-pr-review/${PR}-followup.json" [ -s "/tmp/swe-workbench-pr-review/${PR}-followup.json" ] || { echo "PR #$PR not found or not accessible."; exit 1; } ``` Extract fields from the JSON. The state file is stored under `${PR}-followup.json` (distinct from `${PR}.json` used by the primary review) to allow both to coexist. ```bash JSO