Skip to main content
skill CX Codex

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

Install into Claude Code · Skills CLI (Vercel) All methods and platforms ↓
npx skills add ZaxbyHub/opencode-swarm --skill ci-fix-monitor -a claude-code
Open on GitHub

What 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-code

2Manually: put the files in place

~/.claude/skills/ci-fix-monitor/SKILL.md

Copy the whole skill folder; for one project use .claude/skills/ci-fix-monitor/

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.

ci-fix-monitor ZaxbyHub The ci-fix-monitor skill checks a PR’s CI results, diagnoses failed checks from their logs, and guides fixes and another push. Use it when a PR has red checks. CX Codex +1 ★ 539repo stars gh-fix-ci official openai gh-fix-ci finds failing GitHub Actions checks on a pull request, inspects logs, and drafts a fix plan. The skill modifies code only after explicit approval. CX Codex +1 12,100installs fix react fix is a Claude Code skill that formats changed files and checks for lint errors. Run it before committing to see whether CI checks still need fixes. CX Codex +1 2,300installs openai-gh-fix-ci OpenAI openai-gh-fix-ci inspects failing GitHub Actions checks on pull requests via the gh CLI, extracts error context, and drafts a fix plan. ★ 540repo stars ci-release-stinger Legion Code Inc. ci-release-stinger is a Claude Code skill that designs and reviews CI and release workflows for SvelteKit apps on Vercel and npm packages. It activates for requests about Actions jobs, migrations, caching, or publishing. CX Codex +1 ★ 96repo stars fix-ci cursor fix-ci — a skill for Claude Code, Codex, Cursor, GitHub Copilot, Gemini CLI and OpenCode that hunts down failing PR checks, reads the logs, and applies the smallest fix that moves the needle. CX Codex +1 2,600installs release cyrusagents This skill walks a Cyrus CLI release through trusted publishing: prepare, verify, publish, finish. Useful when a version has to ship without touching packages by hand. CX Codex +1 870installs

From the same set121

The whole set →
swarm-ci-monitor 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. CX Codex +1 ★ 539repo stars commit-pr commit-pr — a checklist the agent must clear before it commits, pushes or opens a PR. Built for the case where an AI agent publishes the branch, not a person. CX Codex +1 ★ 539repo stars skill-edit-validation skill-edit-validation sweeps test suites for stale assertions after modifying skill markdown files, preventing unexpected CI breaks. CX Codex +1 ★ 539repo stars discover This skill delegates repository discovery and maps project rules, code structure, and risk areas. Use it before a complex change when you need to understand the existing project first. CX Codex +1 ★ 539repo stars swarm-resume swarm-resume is a Claude Code skill that restores swarm plan state and clears stale git branches to resume work on an approved plan. CX Codex +1 ★ 539repo stars ci-failure-batching ci-failure-batching collects failed PR checks before planning fixes. Use it to group related CI problems and avoid a separate push cycle for each one. CX Codex +1 ★ 539repo stars mock-to-internals-migration mock-to-internals-migration is a Claude Code skill for moving mocks from Vitest to Bun and checking the _internals seam. It activates for mock migrations and related test-structure changes. CX Codex +1 ★ 539repo stars gate-attribution gate-attribution assigns reviewer and test engineer verdicts to individual plan tasks during swarm batch runs. Activates when dispatches return multi-task rows. CX Codex +1 ★ 539repo stars

Project sponsors

Companies that keep this analytics open