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

swarm-ci-monitor

Skill517 starsChanged 3 days agoMITView on GitHub

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.

We split this skill into the rules it gives an agent

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

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈2

    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 10
  2. Distinctive:

    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.

    line 29
  3. Distinctive:

    Do not declare victory until the post-merge local-git confirmation (Step 4b) passes.

    line 35

≈ “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.

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.

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