swarm-pr-feedback git:20260719.1e3a712A

Immutable. This exact content is served forever at /api/v1/blob/2c391b2c046eb9b4.

---
name: swarm-pr-feedback
audience: swarm-plugin
description: >
  Claude Code adapter for closing known PR feedback. Use when addressing pasted
  review feedback, GitHub review comments or threads, requested changes,
  CI/check failures, merge conflicts, stale PR branches, or PR follow-up work
  that must verify every claim before fixing it.
---

# Swarm PR Feedback

Read and follow `../../../.opencode/skills/swarm-pr-feedback/SKILL.md` as the canonical workflow.

## Claude Code Execution Notes

- **Batch-collect all CI failures before proposing any fix** (Issue #1746). On GitHub, run `gh pr checks <n> --json name,bucket,state,link`, filter to `bucket == "fail" || bucket == "cancel"`, then fetch each failed log with `gh run view <run-id> --log-failed`. On other hosts, use the host-equivalent API. Build the complete failure ledger before triaging or proposing fixes — do not iterate check-by-check through push cycles.
- Check out the PR branch locally before verifying or fixing anything. Fetch the head ref if absent, confirm the working tree is clean, then verify against the PR branch rather than the base branch.
- Build the complete feedback ledger before editing: pasted feedback, GitHub comments/threads, requested changes, CI/check failures, merge conflicts, stale branch state, PR body claims, linked issues, commits, and any validated `swarm-pr-review` handoff artifact.
- Treat every feedback item as a claim until source evidence, tests, logs, or PR metadata prove or disprove it.
- Preserve original finding IDs and reviewer/critic provenance from review handoff artifacts.
- For async verification lanes, treat `output` as a preview and call `retrieve_lane_output` for the full `output_ref` artifact before classifying or resolving feedback. Retry coverage gaps through the same structured mode; direct Task-tool dispatch is not equivalent because it loses durable phase and revision provenance. If the gap cannot be closed, stop and surface the affected items as BLOCKED.
- Do not resolve GitHub review threads unless the user explicitly instructs it.
- **Mandatory gates — Stage A and Stage B (+ closeout).** Stage A always runs exact `git diff --check` plus a targeted reproduction/regression, and also runs every build, typecheck, and lint/format category mechanically discovered from the repository; it never invents a no-op category to reach a fixed count. Stage B (independent `reviewer` + `test_engineer` on the Stage-A-green diff) is mandatory for any change made as part of this process, followed by the separate reviewer + critic closeout gate on the Stage-B-approved diff. Record both closeout verdicts in the runtime's session task-gates artifact using the repository/runtime-specific durable-session guidance; `.swarm/` is plugin runtime state — do not write task artifacts there.
- When the plugin's mechanical tools are available, use `run_pr_feedback_stage_a`, then the exact ordered `swarm-pr-feedback:stage-b-reviewer`, `:stage-b-test`, `:closeout-reviewer`, and `:closeout-critic` structured modes from the canonical skill. Free-form verdict prose is not equivalent evidence, and any edit restarts the sequence at Stage A.
- Descendant coder and nested child sessions inherit the parent mechanical gate;
  delegation never grants early commit, push, remote-write, checkout, or
  protected-evidence authority.
- Stage A must execute one proof command on every run: use the exact failing CI/test reproduction when available; otherwise run a repo-appropriate targeted regression/test command for the changed behavior. With `run_pr_feedback_stage_a`, declare the exact test/package/path selector in `targets` and every concrete discovered workspace/category/source obligation with its `working_directory` and `obligation_id`. Standard contained Gradle/Maven wrappers and exact bounded `.pr-validation.json` contract validators are supported only when byte-identical to the immutable `base_ref`/`base_sha` merge-base copy; arbitrary, no-op, mutating, publishing, PR-authored, unverified opaque, fix/update, or selector-free commands fail closed, and every command is checked against unchanged content, HEAD, index, refs, upstream, and Git config.
- After local gates pass, create the reviewed commit with one standalone `git commit`, then call `complete_pr_workflow` once. It fails closed unless the index/worktree are clean and HEAD is a non-merge direct child whose sole parent is the immutable intake head; otherwise it binds that commit to the intended upstream remote-tracking ref and arms publication. Push only with the canonical single-ref form `git push <bound-remote> <bound-commit>:refs/heads/<bound-branch>`; force flags, aliases, wrappers, fetch-based local-ref forgery, extra refspecs, and other remote writes fail closed. Call `complete_pr_workflow` a second time immediately after read-only verification of both the actual remote ref and its local tracking ref proves they point to that exact commit; only then perform explicitly authorized PR comment/body/thread writes.
- Emit the user-facing final response only after the second completion call
  clears the durable gate. Until then, architect response text is mechanically
  replaced and an idle parent session is resumed rather than allowed to stop.
- If the verification bind is genuinely unreachable (PR head cannot be
  fetched/checked out, or a compound `git fetch … && git checkout …` keeps
  being rejected — run them as TWO separate standalone commands first), call
  `abort_pr_workflow` with `mode: "PR_FEEDBACK"` and a one-line `reason`
  instead of looping. The tool refuses while PR workflow lanes are in flight
  and refuses once `prFeedbackReadyToPublish` is armed — after arming, you
  MUST complete via `complete_pr_workflow` because aborting an armed gate
  would drop the immutable-commit binding and leave a half-published commit.
  The user can also run `/swarm abort-pr-workflow` once the wake budget
  suspends. Never abort as a gate-skip shortcut.
- Use the repository commit/PR workflow before pushing or updating the PR.

Final output must include a closure ledger for every original feedback item,
including conflicts, stale branch state, obsolete CI, and generated-output drift
when they affected the PR.