ci-fix-monitor · zaxbyhub — Claude Code skill: what it does, how to install
ci-fix-monitor is a Claude Code skill that monitors pull request check runs and resolves CI failures. It tracks builds until every required job turns green.
MIT ★ 539 updated 2026-10-29
npx skills add ZaxbyHub/opencode-swarm --skill ci-fix-monitor -a claude-codeWhat ci-fix-monitor does
ci-fix-monitor tracks GitHub Actions check runs on pull requests and repairs build breakages. It handles package-check tarball validation errors, linter issues, and cross-platform macOS file I/O failures.
Because the environment lacks the gh CLI, the skill fetches job logs using MCP tools like mcp__github__pull_request_read and mcp__github__get_job_logs. Formatter fixes are applied strictly to targeted files using bunx biome format --write <specific-file>, without whole-repo formatting. Generated output in dist/ is never committed; local builds with bun run build serve only to verify bundle imports before running bun test <file>.
What it helps with
- inspect failing GitHub Actions check runs via MCP tools
- fix package-check issues during npm tarball validation
- repair source code formatting with Bun and Biome
- rebase branches onto main when encountering version drift
Example prompts for the agent
- Check failed CI runs on this PR and fix package-check errors
- Inspect the build logs via GitHub MCP and format the failing files
- Monitor PR checks until green and run tests for modified files
How to install ci-fix-monitor
1Skills CLI (Vercel)
npx skills add ZaxbyHub/opencode-swarm --skill ci-fix-monitor -a claude-code2Manually: put the files in place
~/.claude/skills/ci-fix-monitor/SKILL.mdCopy the whole skill folder; for one project use .claude/skills/ci-fix-monitor/
1Skills CLI (Vercel)
npx skills add ZaxbyHub/opencode-swarm --skill ci-fix-monitor -a codex2Manually: put the files in place
.agents/skills/ci-fix-monitor/SKILL.mdFor all projects use ~/.agents/skills/
1Skills CLI (Vercel)
npx skills add ZaxbyHub/opencode-swarm --skill ci-fix-monitor -a cursor2Manually: put the files in place
.cursor/skills/ci-fix-monitor/SKILL.mdCursor also reads .agents/skills/ and .claude/skills/
1GitHub CLI
gh skill install ZaxbyHub/opencode-swarm .agents/skills/ci-fix-monitor2Manually: put the files in place
.github/skills/ci-fix-monitor/SKILL.md1Skills CLI (Vercel)
npx skills add ZaxbyHub/opencode-swarm --skill ci-fix-monitor -a gemini-cli2Platform CLI
gemini skills install https://github.com/ZaxbyHub/opencode-swarm --path .agents/skills/ci-fix-monitorManually: put the files in place
.devin/skills/ci-fix-monitor/SKILL.mdThe legacy .windsurf/skills/ path still works
Skills CLI (Vercel)
npx skills add ZaxbyHub/opencode-swarm --skill ci-fix-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 ci-fix-monitor
How to install ci-fix-monitor in Claude Code?
Run npx skills add ZaxbyHub/opencode-swarm --skill ci-fix-monitor -a claude-code.
What does ci-fix-monitor do?
It diagnoses failed GitHub Actions checks on pull requests, pulls logs using MCP endpoints, and fixes formatting, build, or rebase issues.
What is required to run ci-fix-monitor?
It requires GitHub MCP tools (mcp__github__*), Bun runtime for testing and Biome formatting, and git CLI access.
Source text
SKILL.md · MIT
---
name: ci-fix-monitor
description: 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.
metadata:
audience: swarm-plugin
---
# CI Fix Monitor
Read `.opencode/skills/ci-fix-monitor/SKILL.md` for the full protocol.
Also load:
1. `.agents/skills/commit-pr/SKILL.md` before committing or pushing any fix
2. `.agents/skills/engineering-conventions/SKILL.md` if the fix touches source files
3. `.agents/skills/running-tests/SKILL.md` before running any test suite as part of a fix
Codex-specific 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 available. Use `mcp__github__pull_request_read` (method `get_check_runs`) to list check status and `mcp__github__get_job_logs` (with `return_content: true`) to fetch failure logs.
- For `package-check` failures: `package-check` validates the npm tarball (`npm pack` + tarball contents). A failure is a source/build/package-manifest problem, not generated-file drift. `dist/` is generated and NOT committed — do not stage it; run `bun run build` locally only when you need the bundle to verify (e.g. `node --input-type=module -e "await import('./dist/index.js'); console.log('dist import OK')"`). There is no longer a committed-dist drift check.
- For a branch behind main (version-drift): `git fetch origin main && git rebase origin/main` (abort with `git rebase --abort` if conflicts occur and escalate to user), then `git push --force-with-lease origin <branch>`. Force-push is required and expected after rebase.
- For format violations: `bunx biome format --write <specific-file>` — do NOT run `biome format --write .` on the whole repo.
- After any source fix, run the focused test file (`bun test <file>`) before committing.
- Do not declare victory until ALL required checks show green; `skipped` is acceptable only if the same check was skipped on the base branch.
© ZaxbyHub · MIT · ZaxbyHub/opencode-swarm
Similar skills
All skills for Git and GitHub →ci-fix-monitor by other authors comes first.