Swig Test
swig/swig
Run SWIG test suite for specific languages. An agent skill from swig/swig.
Batch collection and fix protocol for CI failures. An agent skill from ZaxbyHub/opencode-swarm.
Install CI Failure Batching
$ npx skills add ZaxbyHub/opencode-swarm --skill ci-failure-batching -a claude-codeProject install by default; add -g for ~/.claude/skills/.
$ gh skill install ZaxbyHub/opencode-swarm ci-failure-batching --agent claude-codeProject scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).
$ git clone --depth 1 https://github.com/ZaxbyHub/opencode-swarm.git skills-src && mkdir -p .claude/skills && cp -r skills-src/.opencode/skills/ci-failure-batching .claude/skills/ci-failure-batching && rm -rf skills-srcUse ~/.claude/skills/ instead of .claude/skills for a personal install. The folder must contain SKILL.md.
Claude Code skills documentation · loads skills from .claude/skills/
Install the "ci-failure-batching" agent skill from https://github.com/ZaxbyHub/opencode-swarm/tree/main/.opencode/skills/ci-failure-batching into .claude/skills/ci-failure-batching/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "ci-failure-batching", then confirm the skill loads.Claude Code copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$skill-installer install https://github.com/ZaxbyHub/opencode-swarm/tree/main/.opencode/skills/ci-failure-batchingType this inside Codex. $skill-installer <name> installs a curated skill from openai/skills. The installer writes to $CODEX_HOME/skills (default ~/.codex/skills). Restart Codex if the skill does not show up.
$ npx skills add ZaxbyHub/opencode-swarm --skill ci-failure-batching -a codexProject install goes to .agents/skills/; add -g for ~/.codex/skills/.
$ gh skill install ZaxbyHub/opencode-swarm ci-failure-batching --agent codexProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/ZaxbyHub/opencode-swarm.git skills-src && mkdir -p .agents/skills && cp -r skills-src/.opencode/skills/ci-failure-batching .agents/skills/ci-failure-batching && rm -rf skills-srcUse ~/.agents/skills/ instead of .agents/skills for a personal install.
Codex skills documentation · loads skills from .agents/skills/
Install the "ci-failure-batching" agent skill from https://github.com/ZaxbyHub/opencode-swarm/tree/main/.opencode/skills/ci-failure-batching into .agents/skills/ci-failure-batching/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "ci-failure-batching", then confirm the skill loads.Codex copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add ZaxbyHub/opencode-swarm --skill ci-failure-batching -a cursorProject install goes to .agents/skills/; add -g for ~/.cursor/skills/.
$ gh skill install ZaxbyHub/opencode-swarm ci-failure-batching --agent cursorProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/ZaxbyHub/opencode-swarm.git skills-src && mkdir -p .cursor/skills && cp -r skills-src/.opencode/skills/ci-failure-batching .cursor/skills/ci-failure-batching && rm -rf skills-srcUse ~/.cursor/skills/ instead of .cursor/skills for a personal install.
Cursor skills documentation · loads skills from .cursor/skills/, .agents/skills/, .claude/skills/, .codex/skills/
Install the "ci-failure-batching" agent skill from https://github.com/ZaxbyHub/opencode-swarm/tree/main/.opencode/skills/ci-failure-batching into .cursor/skills/ci-failure-batching/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "ci-failure-batching", then confirm the skill loads.Cursor copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gemini skills install https://github.com/ZaxbyHub/opencode-swarm.git --path .opencode/skills/ci-failure-batching--scope user (default) or --scope workspace; --path is the subfolder of the repo that holds the skill; --consent skips the security confirmation prompt.
$ npx skills add ZaxbyHub/opencode-swarm --skill ci-failure-batching -a gemini-cliProject install goes to .agents/skills/; add -g for ~/.gemini/skills/.
$ gh skill install ZaxbyHub/opencode-swarm ci-failure-batching --agent gemini-cliProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/ZaxbyHub/opencode-swarm.git skills-src && mkdir -p .gemini/skills && cp -r skills-src/.opencode/skills/ci-failure-batching .gemini/skills/ci-failure-batching && rm -rf skills-srcUse ~/.gemini/skills/ instead of .gemini/skills for a personal install, then run /skills reload.
Gemini CLI skills documentation · loads skills from .gemini/skills/, .agents/skills/
Install the "ci-failure-batching" agent skill from https://github.com/ZaxbyHub/opencode-swarm/tree/main/.opencode/skills/ci-failure-batching into .gemini/skills/ci-failure-batching/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "ci-failure-batching", then confirm the skill loads.Gemini CLI copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gh skill install ZaxbyHub/opencode-swarm ci-failure-batchingInstalls for Copilot at project scope by default; add --scope user for a personal install. Preview a skill first with gh skill preview. Needs GitHub CLI 2.90.0 or later (public preview).
$ npx skills add ZaxbyHub/opencode-swarm --skill ci-failure-batching -a github-copilotProject install goes to .agents/skills/; add -g for ~/.copilot/skills/.
$ git clone --depth 1 https://github.com/ZaxbyHub/opencode-swarm.git skills-src && mkdir -p .github/skills && cp -r skills-src/.opencode/skills/ci-failure-batching .github/skills/ci-failure-batching && rm -rf skills-srcUse ~/.copilot/skills/ instead of .github/skills for a personal install. Commit .github/skills so cloud agent and code review can use it.
GitHub Copilot skills documentation · loads skills from .github/skills/, .claude/skills/, .agents/skills/
Install the "ci-failure-batching" agent skill from https://github.com/ZaxbyHub/opencode-swarm/tree/main/.opencode/skills/ci-failure-batching into .github/skills/ci-failure-batching/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "ci-failure-batching", then confirm the skill loads.GitHub Copilot copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add ZaxbyHub/opencode-swarm --skill ci-failure-batching -a opencodeOpenCode documents no install command of its own. Project install goes to .agents/skills/; add -g for ~/.config/opencode/skills/.
$ gh skill install ZaxbyHub/opencode-swarm ci-failure-batching --agent opencodeProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/ZaxbyHub/opencode-swarm.git skills-src && mkdir -p .opencode/skills && cp -r skills-src/.opencode/skills/ci-failure-batching .opencode/skills/ci-failure-batching && rm -rf skills-srcUse ~/.config/opencode/skills/ instead of .opencode/skills for a personal install.
OpenCode skills documentation · loads skills from .opencode/skills/, .claude/skills/, .agents/skills/
Install the "ci-failure-batching" agent skill from https://github.com/ZaxbyHub/opencode-swarm/tree/main/.opencode/skills/ci-failure-batching into .opencode/skills/ci-failure-batching/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "ci-failure-batching", then confirm the skill loads.OpenCode copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
Facts
- Skill name
ci-failure-batching- GitHub stars
- 494
- Token cost
- ~607 tokens
- SKILL.md length
- 309 words
- Files
- 1
- Skills in repo
- 91
- Repo updated
- First seen
- Licence
- MIT
At a glance
Batch collection and fix protocol for CI failures. An agent skill from ZaxbyHub/opencode-swarm.
- Works in 6 steps: DO NOT immediately fix the first… → If jobs are still running: Note the… → Once the run completes, collect ALL… → …
- Tasks that involve Failing and flaky tests
- SKILL.md covers Trigger, Protocol, Why this matters and Pr-monitor expectation
- Calls gh and git
What it does
CI Failure Batching is an agent skill from ZaxbyHub/opencode-swarm. Batch collection and fix protocol for CI failures. Triggered when any CI check fails on a PR. Prevents serial diagnose-fix-push cycles by collecting all failures before fixing.
Its SKILL.md is about 610 tokens, which your agent loads only when the skill is triggered. It is a single SKILL.md file with no bundled scripts.
It sits in Testing & QA, covering Failing and flaky tests. The repository describes itself as: Architect-centric agentic swarm plugin for OpenCode. Hub-and-spoke orchestration with SME consultation, code generation, and QA review. The licence is MIT.
When your agent uses it
- Tasks that involve Failing and flaky tests
Example prompts
- “/ci-failure-batching”
Workflow steps
6 steps, taken from the first numbered list in SKILL.md.
- DO NOT immediately fix the first failure. Check if other jobs are still running
- If jobs are still running: Note the failure, WAIT for the run to complete
- Once the run completes, collect ALL failures
- Fix ALL failures in one changeset: Cluster by root cause, fix each cluster, verify locally
- Publish through commit-pr. This skill owns diagnosis and fix-planning
- Only re-push if NEW failures surface that were not in the original batch.
What it can do on your machine
Read from SKILL.md and the folder at commit b63a4bd. It shows what the files ask for, not the result of running them.
Tool permissions
Pre-approves nothing: there is no allowed-tools line, so your agent's usual permission prompts apply.
From allowed-tools in the SKILL.md frontmatter.
Runs code
Shell commands in SKILL.md call:
ghgit
From the folder's file list and the shell code blocks in SKILL.md.
Network
No URLs in SKILL.md. Its commands use gh and git, which can reach the network depending on how they are called.
From URLs in SKILL.md, links to its own repository left out.
Credentials
Names no API keys, tokens, secrets or passwords.
From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.
Context cost
CI Failure Batching loads about 607 tokens when it runs. Until then it costs about 49 tokens; SKILL.md has 309 words of instructions outside code blocks.
Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.
Safety
Auto-check passed
The automated check found no risky patterns in SKILL.md.
Automated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); files beside SKILL.md are not scanned.
SKILL.md
The full file from ZaxbyHub/opencode-swarm at commit b63a4bd, republished under its MIT licence (© ZaxbyHub). 309 words, ~607 tokens.
Download SKILL.mdSave it as
.claude/skills/ci-failure-batching/SKILL.md (or your agent's skills folder).- name
- ci-failure-batching
- description
- Batch collection and fix protocol for CI failures. Triggered when any CI check fails on a PR. Prevents serial diagnose-fix-push cycles by collecting all failures before fixing.
- audience
- swarm-plugin
CI Failure Batching
Trigger
When the PR monitor surfaces pr.ci.failed. The event is batched after the
check set is complete and includes all known failed checks in failedChecks.
Protocol
- DO NOT immediately fix the first failure. Check if other jobs are still running:
gh pr checks <PR> --repo <repo> - If jobs are still running: Note the failure, WAIT for the run to complete
- Once the run completes, collect ALL failures:
- Identify every check with
failstatus - For each:
gh run view <run-id> --log-failed - Build a complete failure ledger
- Identify every check with
- Fix ALL failures in one changeset: Cluster by root cause, fix each cluster, verify locally
- Publish through
commit-pr. This skill owns diagnosis and fix-planning ONLY (issue #2131 criterion E): before any commit or push, compose thecommit-prskill for the commit message, PR body/invariant-audit/test-plan discipline, and the push protocol. The batching goal is ONE push cycle (collect all → fix all → push once), not literally one commit — a single new commit containing all batched fixes satisfies the goal. Guardrail facts (verified in the tool-before push guardrail): baregit push --forceand-fare deny-pattern-blocked;--force-with-leaseis EXEMPT because it refuses to overwrite remote work gained since your last fetch — commit-pr mandates it for fork/rebase flows. Even so, prefer a normal new fix commit over amending an already-pushed commit. - Only re-push if NEW failures surface that were not in the original batch.
Why this matters
Without batching, N failures produce N push cycles. With batching, N failures produce 1 push cycle.
Example from session #1685:
- Without batching: 6 pushes (format → stale-assertion-1 → stale-assertion-2 → integration → merge-group → clean)
- With batching: 2 pushes (collect all → fix all → push once → clean)
Pr-monitor expectation
The pr-monitor should fire one pr.ci.failed event for the completed failing
check set, not one event per check. Still verify with gh pr checks before
fixing, because GitHub can append late merge-group or matrix jobs.
© ZaxbyHub, MIT. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file
Files
Just SKILL.md in .opencode/skills/ci-failure-batching of ZaxbyHub/opencode-swarm.
Open the folder on GitHubat commit b63a4bd
Compare with similar skills
CI Failure Batching next to the 5 skills that share the most tags, products or categories with it. Stars are the repository's; “used in” counts other GitHub owners with a copy.
| Skill | Stars | Used in | Tokens | Auto-check | Licence | Repo updated |
|---|---|---|---|---|---|---|
| CI Failure Batching this skillZaxbyHub/opencode-swarm | 494 | — | ~607 | Automated safety check: Pass | MIT | |
| Swig Testswig/swig | 6.3k | — | ~2.3k | Automated safety check: Pass | Custom licence | |
| Triage CI FailureDataDog/datadog-agent | 3.8k | — | ~2.3k | Automated safety check: Pass | Apache-2.0 | |
| Dynamo Jira TicketDynamoDS/Dynamo | 2k | — | ~1.1k | Automated safety check: Pass | Apache-2.0 | |
| Fix Ready PRsfastrepl/anarlog | 9.5k | — | ~1.4k | Automated safety check: Pass | MIT | |
| Trx Analysismicrosoft/vstest | 969 | — | ~1.8k | Automated safety check: Pass | MIT |
Similar skills
- Official
Triage CI Failure
DataDog/datadog-agent
Classify a failed CI as either caused by an active incident, flakiness, or a true code regression.
Dynamo Jira Ticket
DynamoDS/Dynamo
Create structured Jira tickets for Dynamo from bug reports, failing tests, or feature requests.
Fix Ready PRs
fastrepl/anarlog
Inspect every open non-draft PR for CI failures and unresolved Cursor Bugbot findings, then fix them on the existing PR branches.
- Official
Trx Analysis
microsoft/vstest
Parse and analyze Visual Studio TRX test result files. An agent skill from microsoft/vstest.
Wio
workersio/skills
Testing workflow skill for finding high-value test candidates, writing focused tests, generating realistic workloads, reviewing test value, and diagnosing test-suite health.
More from ZaxbyHub/opencode-swarm
All 91 skills in this repoCodebase Review Swarm
ZaxbyHub/opencode-swarm
Runs an evidence-gated, quote-grounded audit of a codebase for security, QA, accessibility, performance and more, and writes a verified report without changing source files.
Issue Tracer
ZaxbyHub/opencode-swarm
Drives a bug report from validation and root-cause tracing through a critic-reviewed plan, an approved minimal fix and a PR-ready closure, never merging without recorded human approval.
Commit and PR Publishing for Codex
ZaxbyHub/opencode-swarm
Codex adapter for opencode-swarm that governs commits, pushes, draft PRs, PR body updates and CI closeout, deferring to the repo's canonical commit-pr protocol.
Durable Session State
ZaxbyHub/opencode-swarm
Keeps plans, decisions, evidence and reviewer verdicts in small files so long multi-phase tasks survive context compaction and session resumes.
Swarm PR Feedback Closer
ZaxbyHub/opencode-swarm
Ingests existing pull request feedback such as review comments and CI failures, verifies each claim, fixes confirmed issues and reports closure status for every item.
Swarm PR Subscribe
ZaxbyHub/opencode-swarm
Monitor a pull request after creation and act autonomously on pushed PR activity.
Related
Categories
Questions about CI Failure Batching
What does CI Failure Batching do?
Batch collection and fix protocol for CI failures. An agent skill from ZaxbyHub/opencode-swarm. CI Failure Batching is an agent skill from ZaxbyHub/opencode-swarm. Batch collection and fix protocol for CI failures.
When should I use CI Failure Batching?
CI Failure Batching fits situations like: tasks that involve Failing and flaky tests.
How do I install CI Failure Batching in Claude Code?
Run `npx skills add ZaxbyHub/opencode-swarm --skill ci-failure-batching -a claude-code`. Or copy the skill folder (.opencode/skills/ci-failure-batching in ZaxbyHub/opencode-swarm) into .claude/skills/ci-failure-batching in your project. Claude Code loads it when a task matches its description.
How do I install CI Failure Batching in Codex?
Run `npx skills add ZaxbyHub/opencode-swarm --skill ci-failure-batching -a codex`. Or copy the skill folder (.opencode/skills/ci-failure-batching in ZaxbyHub/opencode-swarm) into .agents/skills/ci-failure-batching in your project. Codex loads it when a task matches its description.
Can I use CI Failure Batching in Cursor, Gemini CLI or GitHub Copilot?
Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add ZaxbyHub/opencode-swarm --skill ci-failure-batching -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/ci-failure-batching, .gemini/skills/ci-failure-batching, .github/skills/ci-failure-batching and .opencode/skills/ci-failure-batching in your project.
What does CI Failure Batching need to run?
Going by SKILL.md and its folder, CI Failure Batching needs the command-line tools its instructions call (gh and git).
Does CI Failure Batching access the network?
SKILL.md contains no URLs. Its commands use gh and git, which can reach the network depending on how they are called. This is read from the text; nothing was executed.
Is CI Failure Batching safe to install?
Our automated static check of SKILL.md found no risky patterns, such as piping downloads into a shell, reading credential files or hidden Unicode. It is not a guarantee. Review the folder before installing.
What licence does CI Failure Batching use?
CI Failure Batching is published under the MIT licence (the repository's licence). It allows redistribution, so the full SKILL.md is shown on this page.
How many tokens does CI Failure Batching use?
About 607 tokens (SKILL.md is roughly 2.4k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full.
What are the alternatives to CI Failure Batching?
Skills that share tags, products or a category with CI Failure Batching: Swig Test (swig/swig, 6.3k stars), Triage CI Failure (DataDog/datadog-agent, 3.8k stars), Dynamo Jira Ticket (DynamoDS/Dynamo, 2k stars) and Fix Ready PRs (fastrepl/anarlog, 9.5k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.
Who maintains CI Failure Batching?
ZaxbyHub (a GitHub organization) maintains it in ZaxbyHub/opencode-swarm, which has 494 GitHub stars. The repository holds 91 skills in this directory. The repository was last updated on October 10, 2026.
Source: ZaxbyHub/opencode-swarm on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.