Run any Skill in Manus with one click

swarm-pr-feedback

Stars394

Forks40

UpdatedJuly 11, 2026 at 07:45

Codex adapter for closing known PR feedback in opencode-swarm. 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.

Installation

Install with Codex or Claude Copy this prompt, paste it into Codex, Claude, or another assistant, and let it review the skill page and install it for you.

Run Skill in Manus

Source

ZaxbyHub

ZaxbyHub/opencode-swarm

View GitHub Repository View Creator Repositories

Download

Run Skill in Manus

Related occupationsSOC

Based on SOC occupation classification

Software DevelopersComputer and Mathematical Occupations·SOC 15-1252

File Explorer

2 files

SKILL.md

readonly

name	swarm-pr-feedback
audience	swarm-plugin
description	Codex adapter for closing known PR feedback in opencode-swarm. 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.

Swarm PR Feedback

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

Codex 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.
Mandatory gates — Stage A and Stage B (+ closeout). Stage A (structural pre-checks: build, typecheck, lint/format, git diff --check, reproduce the failing CI/test command) and Stage B (independent reviewer + test_engineer on the Stage-A-green diff) are MANDATORY for any change made as part of this process, followed by the separate reviewer + critic closeout gate on the Stage-B-approved diff. No fix lands, no closure ledger row is marked FIXED, and no PR is published until all three gates pass on the current diff. See the canonical "Mandatory Gates" section for the full protocol. Record both closeout verdicts in .claude/session/tasks/<slug>/gates.md per durable-session-state (.swarm/ is plugin runtime state — do not write task artifacts there).
Load $writing-tests before changing tests and $commit-pr 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.

More from this repository

same repository

engineering-conventions

ZaxbyHub/opencode-swarm

Guidelines and non-negotiable engineering invariants for modifying opencode-swarm. Load before architecture, plugin initialization, subprocess, tool registration, plan durability, .swarm storage, runtime portability, session/global state, guardrails/retry, chat/system message hooks, or release/cache changes. Authoritative source: AGENTS.md at the repo root and docs/engineering-invariants.md.

2026-07-11394

gate-attribution

ZaxbyHub/opencode-swarm

Per-task gate dispatch protocol. Documents single-task attribution plus parseable set-dispatch reviewer/test_engineer rows.

2026-07-11394

ci-fix-monitor

ZaxbyHub/opencode-swarm

Codex adapter for monitoring and fixing CI failures on opencode-swarm PRs. Use when diagnosing failed checks, fixing `package-check` (npm tarball) failures, resolving quality/lint/format errors, fixing macOS cross-platform file I/O failures, or watching a PR until all checks are green.

2026-07-11394

codebase-review-swarm

ZaxbyHub/opencode-swarm

Codex adapter for running 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.

2026-07-11394

commit-pr

ZaxbyHub/opencode-swarm

Mandatory Codex/Copilot publication adapter for opencode-swarm. Use for every GitHub issue assignment that results in code changes, commits, pushes, draft PRs, PR body edits, PR readying, release notes, or CI closeout. Must be loaded before `git push`, `gh pr create`, `gh pr edit`, or `gh pr ready`. Routes to the single canonical source of truth at `.claude/skills/commit-pr/SKILL.md`.

2026-07-11394

contributing

ZaxbyHub/opencode-swarm

Codex adapter for the opencode-swarm contribution checklist. Use when preparing user-visible changes, release note fragments, local validation, branch hygiene, PR checklist items, or contribution-policy compliance before publishing work.

2026-07-11394

name	swarm-pr-feedback
audience	swarm-plugin
description	Codex adapter for closing known PR feedback in opencode-swarm. 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.

Swarm PR Feedback

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

Codex 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.
Mandatory gates — Stage A and Stage B (+ closeout). Stage A (structural pre-checks: build, typecheck, lint/format, git diff --check, reproduce the failing CI/test command) and Stage B (independent reviewer + test_engineer on the Stage-A-green diff) are MANDATORY for any change made as part of this process, followed by the separate reviewer + critic closeout gate on the Stage-B-approved diff. No fix lands, no closure ledger row is marked FIXED, and no PR is published until all three gates pass on the current diff. See the canonical "Mandatory Gates" section for the full protocol. Record both closeout verdicts in .claude/session/tasks/<slug>/gates.md per durable-session-state (.swarm/ is plugin runtime state — do not write task artifacts there).
Load $writing-tests before changing tests and $commit-pr 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.