swarm-pr-feedback
Swarm PR Feedback provides automated review and iteration workflows for pull requests, integrating feedback from GitHub reviews, CI checks, and branch conflicts. Use it when a PR requires multiple rounds of corrections, needs consistency verification across files, or requires coordinated resolution of reviewer comments and test failures within a structured feedback-collection and fix-delegation process.
git clone --depth 1 https://github.com/ZaxbyHub/opencode-swarm /tmp/swarm-pr-feedback && cp -r /tmp/swarm-pr-feedback/.claude/skills/swarm-pr-feedback ~/.claude/skills/swarm-pr-feedbackSKILL.md
# Swarm PR Feedback Read and follow `../../../.opencode/skills/swarm-pr-feedback/SKILL.md` as the canonical workflow. ## Claude Code Execution Notes - 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 full `output_ref` artifacts before classifying or resolving feedback; degraded or incomplete lane outputs keep the affected items open as evidence gaps. - Do not resolve GitHub review threads unless the user explicitly instructs it. - 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.
>
Run a rigorous, quote-grounded codebase review or security/QA/accessibility/performance/AI-slop/enhancement audit. Use for full-repo or large-subsystem review reports; not for normal implementation. Performs Phase 0 inventory, selected exhaustive tracks with non-diluting depth, coverage closure, reviewer/critic validation, and writes .swarm/review-v8 artifacts without modifying source files.
>
>
Guardrail patterns for opencode-swarm — pattern structure, bypass surfaces, regex anti-patterns, and test conventions for checkDestructiveCommand()
Use when asked to trace, investigate, root-cause, plan, fix, close, or prepare a PR for a GitHub issue or bug report. Runs an evidence-first issue workflow: GitHub intake, reproduction, reasoning-guided localization, no-gap fix planning, independent critic review, user approval gate, implementation, tests, and PR-ready closure.
>
>