fix-pr

Sub-agent contract

/contract

fix-pr turns "review feedback / red CI on PR N" into a pushed fix commit with test evidence, using worktree isolation so the operator's working tree is never disturbed. It is the composition the operator previously chained by hand: /resolve-style feedback interpretation + managed worktree + budget-bounded fix subagent + test gate + push.

Skip when: the fix is a one-line suggestion the operator pointed at directly (apply inline); the PR is already green with all threads resolved (report and stop); or the work is local-only and unpushed (use /ship).

---

Phase 0 — Input gate & preflight (inline, fail closed)

Parse $ARGUMENTS:

• pr — PR number or URL (required). If absent, stop: "fix-pr requires a PR number or URL."
• repo — repo path from --repo; default: current working directory's git root.
• no_push — from --no-push: produce the fix in a kept worktree + diff summary, no remote mutation.
• re_review — from --re-review: after pushing, re-trigger /review (top-level only — see Phase 6 guard).

Preflight (all inline bash; any failure → Blocked, do not improvise):

1. gh auth status — must be authenticated. Fail closed if not.
2. gh pr view <pr> --json state,headRefName,headRepositoryOwner,isCrossRepository,mergeable,url — PR must be OPEN.
3. Fork guard: if isCrossRepository is true and the authenticated account cannot push to the head repo, emit Blocked naming the fork and stop. Never attempt workarounds.
4. Record head_branch — this is the ONLY branch this skill will ever push to.

---

Phase 1 — Feedback harvest (inline)

Reviewer feedback lives in three distinct GitHub stores — miss any one and the fix is silently partial. Harvest all three, then the gates:

1. Inline review comments: gh api repos/{owner}/{repo}/pulls/<pr>/comments — comments anchored to a diff line (each carries path/line/diff_hunk).
2. Review summary bodies: gh pr view <pr> --json reviews — the top-level body of each APPROVE / REQUEST_CHANGES / COMMENT review submission.
3. Issue-level conversation comments: gh pr view <pr> --json comments (equivalently gh api repos/{owner}/{repo}/issues/<pr>/comments). A PR is also an issue, and its plain conversation comments ("also update the docs", "rename this before merge") live on the issues endpoint — the pulls/<pr>/comments endpoint does NOT return them. Skipping this source is the known gap: reviewers who leave feedback as normal PR comments are otherwise dropped entirely, and a PR can have actionable conversation comments with zero inline review comments.