agentleFS
Sign inStart free
ZaxbyHubZaxbyHub/opencode-swarm/.claude/skills/swarm-ci-monitor/SKILL.md

swarm-ci-monitor

Skill517 starsChanged 3 days agoMITView on GitHub

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.

We split this skill into the rules it gives an agent

2 rules. About 0 are common, 1 is distinctive, and 1 is very specific to this project.

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈1

    Distinctive · estimate

    This author's own choices. Worth a look.

  • 1

    Very specific

    Tied to their project's names, files or tools. Probably skip.

  • Common
  • Distinctive
  • Very specific
  1. Very specific:

    Read and follow ../../../.opencode/skills/swarm-ci-monitor/SKILL.md as the canonical workflow.

    line 17
  2. Distinctive:

    Do not declare victory on green checks alone — Step 4b's local-git confirmation, via a different system than the GitHub API, is the …

    line 33

≈ “Common” is an estimate: at least 1 in 5 of the 308,232 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
SKILL.md

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.

Download now (ZIP)

Does it work?

Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.

No reviews yet

People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.

  • It worked
  • Partly
  • It didn't
What did you use it for? e.g. Reviewing pull requests in a Rails app

Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.

Your trail

Files you open will collect here, so you can find them again.

Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.

Now do this for your own.

Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.

Check your setup, free