New: 98,000+ skills indexed from GitHub repos with 100+ stars · every skill safety-checkedBrowse top skillsTop skills
Esc to closeBrowse all skills
Submit a skillBrowse skills
Submit a skillBrowse skills

Agent skill

Merge Queue Readiness

by ZaxbyHub in ZaxbyHub/opencode-swarm

Pre-queue merge-group CI simulation. An agent skill from ZaxbyHub/opencode-swarm.

MITAuto-check passedTesting & QA

Install Merge Queue Readiness

skills CLI
$ npx skills add ZaxbyHub/opencode-swarm --skill merge-queue-readiness -a claude-code

Project install by default; add -g for ~/.claude/skills/.

GitHub CLI
$ gh skill install ZaxbyHub/opencode-swarm merge-queue-readiness --agent claude-code

Project scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).

Manual copy
$ git clone --depth 1 https://github.com/ZaxbyHub/opencode-swarm.git skills-src && mkdir -p .claude/skills && cp -r skills-src/.opencode/skills/merge-queue-readiness .claude/skills/merge-queue-readiness && rm -rf skills-src

Use ~/.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/

Facts

Skill name
merge-queue-readiness
GitHub stars
494
Token cost
~763 tokens
SKILL.md length
382 words
Files
1
Skills in repo
91
Repo updated
First seen
Licence
MIT

At a glance

Pre-queue merge-group CI simulation. An agent skill from ZaxbyHub/opencode-swarm.

  • Works in 7 steps: Fetch latest main: git fetch origin main → Run the simulation command (preferred) → Manual fallback: If the command is… → …
  • Tasks that involve Integration testing
  • SKILL.md covers Trigger, Protocol, Why this matters and Automation
  • Calls bun and git

What it does

Merge Queue Readiness is an agent skill from ZaxbyHub/opencode-swarm. Pre-queue merge-group CI simulation. Triggered before adding a PR to a GitHub merge queue. Prevents merge-queue kick-outs from integration test failures.

Its SKILL.md is about 760 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 Integration testing and Git worktrees. It works with GitHub and Git. 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 Integration testing
  • Tasks that involve Git worktrees

Example prompts

  • “/merge-queue-readiness”

Workflow steps

7 steps, taken from the first numbered list in SKILL.md.

  1. Fetch latest main: git fetch origin main
  2. Run the simulation command (preferred)
  3. Manual fallback: If the command is unavailable, create a temporary simulation worktree (do NOT mutate the PR branch). The default worktree…
  4. Run integration + unit tests against the merged result
  5. If failures: Fix on the PR branch, re-push, re-simulate. Always run the cleanup step (6) before re-simulating or on any exit path — do not…
  6. Cleanup for manual fallback (run on EVERY exit path, including failure): Prefer non-force git worktree remove…
  7. Only after simulation passes, add PR to the merge queue.

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:

    • bun
    • git

    From the folder's file list and the shell code blocks in SKILL.md.

  • Network

    No URLs in SKILL.md. Its commands use 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

Merge Queue Readiness loads about 763 tokens when it runs. Until then it costs about 44 tokens; SKILL.md has 382 words of instructions outside code blocks.

Always · name and description, kept in context so the agent knows when to use it
~44
When it runs · the whole SKILL.md, loaded when a task matches
~763

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). 382 words, ~763 tokens.

Download SKILL.mdSave it as .claude/skills/merge-queue-readiness/SKILL.md (or your agent's skills folder).
name
merge-queue-readiness
description
Pre-queue merge-group CI simulation. Triggered before adding a PR to a GitHub merge queue. Prevents merge-queue kick-outs from integration test failures.
audience
swarm-plugin

Merge Queue Readiness

Trigger

Before adding the PR to the merge queue (or before the final push if the repo uses a merge queue).

Protocol

  1. Fetch latest main: git fetch origin main
  2. Run the simulation command (preferred):
    /swarm ci-simulate [<pr-ref>]
    The optional positional <pr-ref> is the PR branch/ref to simulate (defaults to the current branch). It does NOT accept --base/--head flags. The command runs fixed local gates: bun run typecheck, bun run lint, bun run build, then a full-batch bun test. It creates a temporary detached worktree under os.tmpdir()/swarm-ci-simulate (a SIBLING of the project root, not project-relative), merges the PR ref, runs the gate sequence, removes the worktree, and prunes metadata. It does not accept arbitrary shell commands and does NOT replicate CI's quarantine/retry semantics — it is a fast pre-merge signal, not a CI parity check.
  3. Manual fallback: If the command is unavailable, create a temporary simulation worktree (do NOT mutate the PR branch). The default worktree base is a SIBLING of the project root (<parent>/.swarm-worktrees/), overridable via the worktree_dir config; on Windows, very long paths may be shortened to os.tmpdir()/swwt/.... Place the worktree under that base. Do NOT hardcode /tmp — it does not exist on Windows.
    git worktree add ../.swarm-worktrees/merge-sim origin/main
cd ../.swarm-worktrees/merge-sim
git merge <pr-branch> --no-edit
  4. Run integration + unit tests against the merged result:
    bun test tests/integration --timeout 120000
bun test tests/unit --timeout 120000
    (Use per-file loops for hot modules per AGENTS.md invariant 6)
  5. If failures: Fix on the PR branch, re-push, re-simulate. Always run the cleanup step (6) before re-simulating or on any exit path — do not leave the simulation worktree behind.
  6. Cleanup for manual fallback (run on EVERY exit path, including failure): Prefer non-force git worktree remove ../.swarm-worktrees/merge-sim. If the removal is blocked or fails, surface the block to the user (the worktree guard fails closed for safety) and run git worktree prune.
  7. Only after simulation passes, add PR to the merge queue.
Show full SKILL.md (82 more words)Show less

Why this matters

PR-branch CI and merge-group CI test DIFFERENT things:

  • PR-branch: tests the PR head commit in isolation
  • Merge-group: tests a temporary merge of PR head + latest main

Integration tests that pass on the PR branch may fail in merge-group context due to test interactions exposed by the merged result.

Automation

/swarm ci-simulate automates the merge-result worktree, merge, command run, worktree removal, and metadata prune. Use the manual protocol only when the command is unavailable or the repo needs bespoke setup.

© 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/merge-queue-readiness of ZaxbyHub/opencode-swarm.

Open the folder on GitHubat commit b63a4bd

Compare with similar skills

Merge Queue Readiness 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.

Merge Queue Readiness compared with similar skills
SkillStarsUsed inTokensAuto-checkLicenceRepo updated
Merge Queue Readiness this skillZaxbyHub/opencode-swarm494—~763Automated safety check: PassMIT
Reprovaadin/flow-components129—~1.3kAutomated safety check: PassNone
Fixexercism/website549—~1.2kAutomated safety check: NotesAGPL-3.0
Pre-Release PR Triagejamiepine/voicebox57k—~3.1kAutomated safety check: PassMIT
Ff Worktreesdamus-io/damus2.1k—~451Automated safety check: PassGPL-3.0
Clean Complete Branchesjtenniswood/espcontrol1.1k—~820Automated safety check: PassCustom licence

Similar skills

  • Repro

    vaadin/flow-components

    Reproduce a Vaadin Flow component bug from a GitHub issue in vaadin/flow-components or a component-specific issue in vaadin/flow.

    129 GitHub stars~1.3k tokensUpdated yesterday
    Testing & QAAuto-check passed

  • Fix

    exercism/website

    Fix a GitHub issue end-to-end — fetches issue, creates worktree, plans and implements fix, runs validation, opens PR, cleans up.

    549 GitHub stars~1.2k tokensUpdated 3 days ago
    DevelopmentAuto-check: notes

  • Pre-Release PR Triage

    jamiepine/voicebox

    Sorts a backlog of open pull requests into must-merge, candidate, superseded and deferred, writes a triage doc and works the merge loop before a release.

    57k GitHub stars~3.1k tokensUpdated 4 days ago
    DevelopmentAuto-check passed

  • Ff Worktrees

    damus-io/damus

    Fast-forward master and every git worktree branch up to a target ref (default github/master), skipping any worktree with unmerged commits.

    2.1k GitHub stars~451 tokensUpdated 29 days ago
    DevelopmentAuto-check passed

  • Clean Complete Branches

    jtenniswood/espcontrol

    Clean up completed Git branches and worktrees for this repository both locally and on GitHub.

    1.1k GitHub stars~820 tokensUpdated today
    DevelopmentAuto-check passed

  • Clean Merged Branch Folders

    jtenniswood/espcontrol

    Clean up local branch worktree folders for this repository after their branches or pull requests have merged to main.

    1.1k GitHub stars~813 tokensUpdated today
    DevelopmentAuto-check passed

More from ZaxbyHub/opencode-swarm

All 91 skills in this repo

  • Codebase 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.

    496 GitHub stars~2.8k tokensUpdated today
    Auto-check passed

  • 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.

    496 GitHub stars~4.4k tokensUpdated today
    Auto-check passed

  • 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.

    496 GitHub stars~1.6k tokensUpdated today
    Auto-check passed

  • 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.

    496 GitHub stars~896 tokensUpdated today
    Auto-check passed

  • 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.

    496 GitHub stars~14k tokensUpdated today
    Auto-check passed

  • Swarm PR Subscribe

    ZaxbyHub/opencode-swarm

    Monitor a pull request after creation and act autonomously on pushed PR activity.

    496 GitHub stars~2.2k tokensUpdated today
    Auto-check passed

Works with

Categories

Questions about Merge Queue Readiness

What does Merge Queue Readiness do?

Pre-queue merge-group CI simulation. An agent skill from ZaxbyHub/opencode-swarm. Merge Queue Readiness is an agent skill from ZaxbyHub/opencode-swarm. Pre-queue merge-group CI simulation.

When should I use Merge Queue Readiness?

Merge Queue Readiness fits situations like: tasks that involve Integration testing; tasks that involve Git worktrees.

How do I install Merge Queue Readiness in Claude Code?

Run `npx skills add ZaxbyHub/opencode-swarm --skill merge-queue-readiness -a claude-code`. Or copy the skill folder (.opencode/skills/merge-queue-readiness in ZaxbyHub/opencode-swarm) into .claude/skills/merge-queue-readiness in your project. Claude Code loads it when a task matches its description.

How do I install Merge Queue Readiness in Codex?

Run `npx skills add ZaxbyHub/opencode-swarm --skill merge-queue-readiness -a codex`. Or copy the skill folder (.opencode/skills/merge-queue-readiness in ZaxbyHub/opencode-swarm) into .agents/skills/merge-queue-readiness in your project. Codex loads it when a task matches its description.

Can I use Merge Queue Readiness 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 merge-queue-readiness -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/merge-queue-readiness, .gemini/skills/merge-queue-readiness, .github/skills/merge-queue-readiness and .opencode/skills/merge-queue-readiness in your project.

What does Merge Queue Readiness need to run?

Going by SKILL.md and its folder, Merge Queue Readiness needs the command-line tools its instructions call (bun and git).

Does Merge Queue Readiness access the network?

SKILL.md contains no URLs. Its commands use git, which can reach the network depending on how they are called. This is read from the text; nothing was executed.

Is Merge Queue Readiness 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 Merge Queue Readiness use?

Merge Queue Readiness 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 Merge Queue Readiness use?

About 763 tokens (SKILL.md is roughly 3.1k 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 Merge Queue Readiness?

Skills that share tags, products or a category with Merge Queue Readiness: Repro (vaadin/flow-components, 129 stars), Fix (exercism/website, 549 stars), Pre-Release PR Triage (jamiepine/voicebox, 57k stars) and Ff Worktrees (damus-io/damus, 2.1k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.

Who maintains Merge Queue Readiness?

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.