swarm-pr-feedback · zaxbyhub — Claude Code skill: what it does, how to install
swarm-pr-feedback — a skill that resolves pull request review comments, CI failures, and branch conflicts through structured verification stages.
MIT ★ 539 updated 2026-10-29
npx skills add ZaxbyHub/opencode-swarm --skill swarm-pr-feedback -a claude-codeWhat swarm-pr-feedback does
The skill compiles an exhaustive ledger from pasted feedback, GitHub threads, CI failures, and merge conflicts. Every item is treated as an unconfirmed claim until verified against the repository code. Branch checkout requires proving exact remote tracking without force flags or recursive submodule checkout.
Verification relies on strict gates. Stage A executes git diff --check, targeted regression tests reproducing CI failures, and all repository build and linter checks. Any source file modification invalidates prior receipts and forces Stage A to rerun from the start. Stage B and closeout require independent subagent passes to review the diff before publishing.
Changes are committed once and pushed without force flags. The skill avoids resolving GitHub review threads on its own unless explicitly directed by the user.
What it helps with
- address reviewer comments and GitHub PR threads systematically
- reproduce and resolve failing CI check runs
- resolve merge conflicts and reconcile stale PR branches
- run mandatory lint, typecheck, and multi-agent review gates
Example prompts for the agent
- Collect all feedback on this PR branch and resolve the failing checks.
- Fix the reported review issues and run Stage A verification.
- Execute
/swarm pr-feedback <PR_URL> continue from .swarm/pr-review/<run_id>/feedback-handoff.jsonto complete feedback intake.
How to install swarm-pr-feedback
1Skills CLI (Vercel)
npx skills add ZaxbyHub/opencode-swarm --skill swarm-pr-feedback -a claude-code2Manually: put the files in place
~/.claude/skills/swarm-pr-feedback/SKILL.mdCopy the whole skill folder; for one project use .claude/skills/swarm-pr-feedback/
1Skills CLI (Vercel)
npx skills add ZaxbyHub/opencode-swarm --skill swarm-pr-feedback -a codex2Manually: put the files in place
.agents/skills/swarm-pr-feedback/SKILL.mdFor all projects use ~/.agents/skills/
1Skills CLI (Vercel)
npx skills add ZaxbyHub/opencode-swarm --skill swarm-pr-feedback -a cursor2Manually: put the files in place
.cursor/skills/swarm-pr-feedback/SKILL.mdCursor also reads .agents/skills/ and .claude/skills/
1GitHub CLI
gh skill install ZaxbyHub/opencode-swarm .agents/skills/swarm-pr-feedback2Manually: put the files in place
.github/skills/swarm-pr-feedback/SKILL.md1Skills CLI (Vercel)
npx skills add ZaxbyHub/opencode-swarm --skill swarm-pr-feedback -a gemini-cli2Platform CLI
gemini skills install https://github.com/ZaxbyHub/opencode-swarm --path .agents/skills/swarm-pr-feedbackManually: put the files in place
.devin/skills/swarm-pr-feedback/SKILL.mdThe legacy .windsurf/skills/ path still works
Skills CLI (Vercel)
npx skills add ZaxbyHub/opencode-swarm --skill swarm-pr-feedback -a opencodeClaude.ai
Zip the folder and upload it in Settings → Capabilities → Skills
Step by step, with commands for each platform: How to install skills in Claude Code: five ways
Questions about swarm-pr-feedback
How to install swarm-pr-feedback in Claude Code?
Run npx skills add ZaxbyHub/opencode-swarm --skill swarm-pr-feedback -a claude-code in your terminal.
What does swarm-pr-feedback do?
It tracks review items in a structured ledger, verifies each issue, applies fixes, and validates the branch through multi-role inspection gates.
Does the skill automatically resolve GitHub threads?
No. GitHub review conversations stay open unless you explicitly tell the agent to resolve them.
Source text
SKILL.md · MIT
--- name: swarm-pr-feedback description: > Codex adapter for closing known PR feedback in any repository. Use when asked to address pasted review feedback, GitHub review comments or threads, requested changes, CI/check failures, merge conflicts, stale PR branches, or follow-up work that must verify and close all known PR issues. metadata: audience: swarm-plugin --- # Swarm PR Feedback Read and follow `../../../.opencode/skills/swarm-pr-feedback/SKILL.md` as the canonical workflow. ## Codex Execution Notes - Codex and ZCode sessions normally have no mechanical controller tools: that is canonical Profile B, not an error — both runtimes can spawn fresh-context subagents. Never report BLOCKED merely because those tools are absent — run verification lanes and every gate role as fresh independent subagents with the same one-row-per-item verdict contracts, and keep the ledger, ownership partition, and digest accounting yourself in working notes (never under `.swarm/`, which is plugin runtime state). Use Profile C strictly separated sequential passes, with the procedural independence disclosed in the closure ledger, only when the session genuinely lacks a subagent mechanism. - Check out the PR branch locally before dispatching feedback lanes or verifying/fixing anything. Fetch the head ref if absent, preserve or surface all dirty tracked/untracked state, prove full HEAD equals the authoritative PR head SHA, and prove the final branch tracks the intended PR head remote/branch. In Profile A, a detached exact-head intake is valid because the first bind attaches only one unambiguous exact tracking ref; Profiles B/C must establish the branch themselves. Never use force or submodule-recursive checkout. - 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 item as a claim until source evidence proves or disproves it, and preserve original finding IDs and reviewer/critic provenance from handoff artifacts. - For a Profile-A review continuation, require the exact user command `/swarm pr-feedback <PR_URL> continue from .swarm/pr-review/<run_id>/feedback-handoff.json`; its mechanical transition validates terminal review state and creates an unbound feedback gate. The artifact by itself does not authorize writes. - Verification (Profiles B/C): every FB item is owned by exactly one verification lane or pass, each returning one `[FEEDBACK-VERIFIED]` row per owned item with the exact PR head SHA recorded. Under Profile A, when a lane result carries an `output_ref`, treat inline lane `output` as a preview and retrieve the full artifact via the runtime's lane-output retrieval capability before classifying; on any profile, degraded or incomplete lane outputs keep the affected items open as evidence gaps. No edits before verification settles. - Do not resolve GitHub review threads unless the user explicitly instructs it. - **Mandatory gates — Stage A and Stage B (+ closeout) on every profile.** Stage A always runs exact `git diff --check` plus one proof command — the exact failing CI/test reproduction when available, otherwise a repo-appropriate targeted regression/test command — plus every build, typecheck, and lint/format category mechanically discovered from the repository; it never invents a no-op category to reach a fixed count. On Profiles B/C run these commands yourself and record command+output receipts in the ledger; any content change invalidates the receipts and restarts Stage A. Stage B: an independent reviewer role, then a test-engineer role, on the Stage-A-green diff (fresh subagents on B; strictly separated re-derivation passes on C). Closeout: a separate reviewer + critic pair on the Stage-B-approved diff. One verdict row per FB ID at every gate; record both closeout verdicts in the session task-gates artifact per the durable-session guidance. - Only if the session actually exposes the plugin's mechanical tools, run Profile A instead: `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, `complete_pr_workflow` arming, and the bound single-ref push. While that controller is active, direct subagent calls and free-form verdict prose are not equivalent evidence, and any edit restarts the sequence at Stage A. - Publication (Profiles B/C): after all gates pass on the unchanged diff, create one reviewed commit on the PR branch, push exactly that commit with a single non-force push through the repository's commit/PR workflow, then verify read-only that the remote head equals the pushed commit before any PR comment/body/thread write. - Load the repository's test-authoring guidance before changing tests and the repository's PR publication workflow before pushing or updating the PR. Final responses 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.
© ZaxbyHub · MIT · ZaxbyHub/opencode-swarm
Similar skills
All skills for Code review and refactoring →swarm-pr-feedback by other authors comes first.