AugmentClaude

CI Fix Monitor

Monitor and fix continuous integration failures on pull requests automatically.

Installation

  1. Make sure Claude is on your device and in your terminal.

    Skills load from ~/.claude/skills/ when Claude Code starts up — so you need it on your machine first. If you don't have it yet, install it once with the command below, then run claude in any terminal to verify.

    One-time setup
    npm i -g @anthropic-ai/claude-code

    Already have it? Skip ahead.

  2. Paste into Claude Code or into your terminal.

    This copies the whole skill folder into ~/.claude/skills/ci-fix-monitor-zaxbyhub/ — the SKILL.md plus any scripts, reference docs, or templates the skill ships with. Safe default: works for every skill.

    Faster alternative (instruction-only skills)

    Skips the clone and grabs only the SKILL.md file. Don't use this if the skill ships Python scripts, reference markdowns, or asset templates — they won't be downloaded and the skill will fail when it tries to load them.

    Quick install (SKILL.md only)
    Sign up to copy
  3. Restart Claude Code.

    Quit and reopen Claude Code (or any other agent that loads from ~/.claude/skills/). New skills are picked up on startup.

  4. Just ask Claude.

    Skills auto-activate when your request matches the skill's description — no slash command needed. Trigger phrases live in the skill's own frontmatter; you can read them in the “What this skill does” section above.

Prefer to read the source first? Open on GitHub.

When Claude uses it

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.

What this skill does

CI Fix Monitor

Read .opencode/skills/generated/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.

Related skills