merge-queue-readiness

Simulates merge-group CI locally before adding a pull request to a GitHub merge queue.

Updated Sep 14, 2026
One-click install
npx skills add https://github.com/pandejesal/drone-nav-sar --skill merge-queue-readiness-pandejesal
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: merge-queue-readiness
Source: https://github.com/pandejesal/drone-nav-sar/tree/main/.swarm/bundled-skills/merge-queue-readiness
Command: npx skills add https://github.com/pandejesal/drone-nav-sar --skill merge-queue-readiness-pandejesal

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Pull request branch CI and merge-group CI test different things: the PR head in isolation versus a temporary merge of the PR head with the latest main. Integration tests that pass on the PR branch can fail in merge-group context, causing merge-queue kick-outs and wasted CI cycles. ## Core Features & Use Cases - Pre-queue merge simulation: Fetches latest main, merges the PR ref into a temporary detached worktree, and runs the full gate sequence (typecheck, lint, build, tests) against the merged result. - Automated command: The /swarm ci-simulate [<pr-ref>] command automates worktree creation, merge, gate execution, removal, and metadata pruning. - Manual fallback protocol: Step-by-step git worktree instructions for repos where the command is unavailable, including mandatory cleanup on every exit path. - Use Case: Before enqueueing a PR that touches shared integration test fixtures, run the simulation to catch test interactions exposed only by the merged result, fix failures on the PR branch, and re-simulate before queueing. ## Quick Start Ask the assistant to run the merge queue readiness simulation on the current pull request branch before adding it to the merge queue.

Frequently Asked Questions about merge-queue-readiness

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I test a pull request before adding it to a GitHub merge queue?

Run a merge simulation that fetches latest main, merges the PR branch into a temporary git worktree, and executes the full test gates against the merged result. The /swarm ci-simulate command automates this, or you can follow the manual git worktree protocol.

Why do tests pass on my PR branch but fail in the merge queue?

PR-branch CI tests the head commit in isolation, while merge-group CI tests a temporary merge of the PR head with latest main. Integration tests can fail in the merged context due to test interactions that only appear after combining both changes.

What does the /swarm ci-simulate command run?

It 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, merges the PR ref, runs the gates, removes the worktree, and prunes metadata. It does not accept arbitrary shell commands.

Does merge queue simulation replicate CI exactly?

No. The simulation is a fast pre-merge signal, not a CI parity check. It does not replicate CI's quarantine or retry semantics, so rare environment-specific failures may still occur in the actual merge group.

What happens if the simulation worktree cleanup fails?

Prefer non-force git worktree removal first. If removal is blocked, the worktree guard fails closed for safety: surface the block to the user and run git worktree prune. Cleanup must run on every exit path, including failures.