swarm-ci-monitor · zaxbyhub, claude — Claude Code skill: what it does, how to install
swarm-ci-monitor monitors CI runs on approved pull requests, repairs broken checks within five cycles, and merges the branch once tests pass.
MIT ★ 539 updated 2026-10-29
npx skills add ZaxbyHub/opencode-swarm --skill swarm-ci-monitor -a claude-codeWhat swarm-ci-monitor does
This skill handles the final stage of an approved pull request inside opencode-swarm. It watches CI runs via the GitHub CLI tool gh. When test suites fail, the skill parses logs and pulls repair recipes from ci-fix-monitor. Then it commits code updates according to commit-pr guidelines. It repeats this repair loop up to five times.
The agent holds exclusive permission to run gh pr merge within the repository. To avoid merging broken code, it runs pre-flight gates and re-evaluates branch freshness before sending the merge call.
Passing tests in the GitHub API do not trigger an immediate success signal. A local git check acts as an independent safety barrier before the job concludes. Without the gh command-line utility, the agent cannot execute these steps.
What it helps with
- monitor pull request CI runs until all checks turn green
- diagnose test failures and apply code fixes automatically
- merge approved pull requests using
gh pr merge - verify branch status through local git before closing tasks
Example prompts for the agent
- Monitor CI for PR #42, fix failing checks, and merge when green
- Watch the approved pull request, repair broken builds, and finish the merge
- Start CI monitoring on this branch and resolve pipeline failures
How to install swarm-ci-monitor
1Skills CLI (Vercel)
npx skills add ZaxbyHub/opencode-swarm --skill swarm-ci-monitor -a claude-code2Manually: put the files in place
~/.claude/skills/swarm-ci-monitor/SKILL.mdCopy the whole skill folder; for one project use .claude/skills/swarm-ci-monitor/
1Skills CLI (Vercel)
npx skills add ZaxbyHub/opencode-swarm --skill swarm-ci-monitor -a codex2Manually: put the files in place
.agents/skills/swarm-ci-monitor/SKILL.mdFor all projects use ~/.agents/skills/
1Skills CLI (Vercel)
npx skills add ZaxbyHub/opencode-swarm --skill swarm-ci-monitor -a cursor2Manually: put the files in place
.cursor/skills/swarm-ci-monitor/SKILL.mdCursor also reads .agents/skills/ and .claude/skills/
1GitHub CLI
gh skill install ZaxbyHub/opencode-swarm .claude/skills/swarm-ci-monitor2Manually: put the files in place
.github/skills/swarm-ci-monitor/SKILL.md1Skills CLI (Vercel)
npx skills add ZaxbyHub/opencode-swarm --skill swarm-ci-monitor -a gemini-cli2Platform CLI
gemini skills install https://github.com/ZaxbyHub/opencode-swarm --path .claude/skills/swarm-ci-monitorManually: put the files in place
.devin/skills/swarm-ci-monitor/SKILL.mdThe legacy .windsurf/skills/ path still works
Skills CLI (Vercel)
npx skills add ZaxbyHub/opencode-swarm --skill swarm-ci-monitor -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-ci-monitor
How to install swarm-ci-monitor in Claude Code?
Run npx skills add ZaxbyHub/opencode-swarm --skill swarm-ci-monitor -a claude-code.
What does swarm-ci-monitor do?
It monitors CI pipelines for approved pull requests, repairs failing checks across up to five cycles, and executes gh pr merge.
What happens if CI checks keep failing?
The skill stops after a limit of 5 fix iterations if checks remain red.
Source text
SKILL.md · MIT
--- name: swarm-ci-monitor description: > Claude Code adapter for end-to-end CI monitoring of an already-reviewed PR in opencode-swarm. Use when the user wants the swarm to monitor a reviewed-and-approved PR's CI, research every failure exhaustively, fix end-to-end, iterate until green (max 5 cycles), then merge. Composes ci-fix-monitor for fix recipes. This is the first skill in the repo that executes a merge — invoke it deliberately. disable-model-invocation: true metadata: audience: swarm-plugin --- # Swarm CI Monitor Read and follow `../../../.opencode/skills/swarm-ci-monitor/SKILL.md` as the canonical workflow. ## Claude Code Execution Notes - `gh` CLI is available natively; use it directly for every step (checks, merge, git operations) — the canonical's MCP tool-mapping table is for the Codex adapter, not this environment. - This is the first skill in the repo authorized to execute `gh pr merge`. Do not soften or skip the pre-flight gates (Step 1), the pre-merge staleness re-check (Step 3), or the post-merge local-git confirmation (Step 4b) — they are the load-bearing safety mechanism, not optional ceremony. - Load `../commit-pr/SKILL.md` before any commit/push inside the fix loop, and `../../../.opencode/skills/ci-fix-monitor/SKILL.md` for failure-type-specific fix recipes, as the canonical's Composition section directs. - Do not declare victory on green checks alone — Step 4b's local-git confirmation, via a different system than the GitHub API, is the independent gate.
© ZaxbyHub · MIT · ZaxbyHub/opencode-swarm
Similar skills
All skills for Git and GitHub →swarm-ci-monitor by other authors comes first.