swarm-ci-monitor · zaxbyhub — Codex skill: CI monitoring and setup
The swarm-ci-monitor skill monitors CI for an approved, reviewed PR, investigates failures, and works through fixes until checks pass. It can then merge the PR after a final review of its state.
MIT ★ 539 updated 2026-10-29
npx skills add ZaxbyHub/opencode-swarm --skill swarm-ci-monitor -a claude-codeWhat swarm-ci-monitor does
swarm-ci-monitor handles a PR that has already been reviewed and approved. It checks CI, investigates failures, applies fixes, and repeats the cycle until checks pass, for up to five cycles. Before merging, it checks the PR state again; afterward, it must confirm the result through local Git. Passing checks alone are not enough.
In Codex, the skill uses GitHub MCP tools to read check results and job logs. Use ToolSearch to verify that the tools are available; the remote environment does not use gh. Merging requires an available MCP merge tool. If that tool cannot be found, the user must merge manually. Load commit-pr before committing or pushing fixes, and ci-fix-monitor for failure-specific fix recipes.
What it helps with
- check CI for a reviewed and approved PR
- retrieve job logs for failed checks
- investigate failures and apply fixes
- repeat checks and fixes for up to five cycles
- recheck a PR before merging and confirm the result through local Git
Example prompts for the agent
- Monitor CI for this approved PR and fix failures until the checks pass.
- Inspect the failed job logs for this PR and work out the fixes.
- Recheck the PR before merging, then confirm the merge through local Git.
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 .agents/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 .agents/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 do I install swarm-ci-monitor in Codex?
Run npx skills add ZaxbyHub/opencode-swarm --skill swarm-ci-monitor -a codex. The skill file is placed at .agents/skills/swarm-ci-monitor/SKILL.md.
What does swarm-ci-monitor do?
It monitors CI for a reviewed, approved PR, investigates failures, and repeats the fix-and-check cycle for up to five rounds. It then rechecks the PR before merging and confirms the result through local Git.
What is required to merge a PR with swarm-ci-monitor?
Check with ToolSearch that the MCP merge tool is available in the Codex session. If it is unavailable, merge manually; the workflow does not fall back to gh.
Source text
SKILL.md · MIT
--- name: swarm-ci-monitor description: Codex 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. metadata: audience: swarm-plugin --- # Swarm CI Monitor Read and follow `../../../.opencode/skills/swarm-ci-monitor/SKILL.md` as the canonical workflow. ## Codex Execution Notes - MCP tool names (`mcp__github__*`) are injected by the runtime harness and may differ across environments; verify availability via `ToolSearch` before first use in a session. - No `gh` CLI in the remote/MCP environment. Use MCP tools instead: - PR checks → `mcp__github__pull_request_read` method `get_check_runs` - Failure logs → `mcp__github__get_job_logs` with `job_id`, `return_content: true` - PR mergeable/mergeStateStatus/reviewDecision → `mcp__github__pull_request_read` method `get` - **Merge is new surface area.** There is no `mcp__github__merge_pull_request` reference anywhere else in the repo. Verify availability via `ToolSearch` before first use in a session. If the tool is unavailable, do not attempt a fallback that contradicts the "no `gh` CLI" premise above — surface to the user that the merge must be done manually. "`ToolSearch` didn't confirm the tool but I'll try it anyway" is not acceptable for the one action in this skill that cannot be safely undone — surface to the user instead. - Do not soften Step 1's pre-flight gates or Step 3's pre-merge re-check — this is the first skill in the repo authorized to execute a merge. - Load `../commit-pr/SKILL.md` before committing or pushing any fix, 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 until the post-merge local-git confirmation (Step 4b) passes. Green checks alone are not sufficient.
© ZaxbyHub · MIT · ZaxbyHub/opencode-swarm
Similar skills
All skills for DevOps and infrastructure →swarm-ci-monitor by other authors comes first.