Claude Code Merge Queue

Claude Code Merge Queue 🚦

The local, zero-cost merge queue for parallel Claude Code agents. Several
agents land, build, and test at the same time — this serializes it so push
races, redundant heavy builds, and shared-resource test flakiness can't happen.

⚡ Quickstart

Contents

- ⚙️ Configuration
- 🆚 vs. GitHub's Merge Queue
- 🧰 What's in the box
- 🚨 The emergency hatch
- 🔍 Know the limits
- 📄 License

⚙️ Configuration

Everything lives in one file — see
examples/claude-code-merge-queue.config.mjs for every
field with comments. The short version:

A malformed config (empty branch names, a negative port, productionBranch
equal to integrationBranch, ...) fails loud with every problem listed,
the moment any command loads it — not a mysterious failure three steps
later.

🆚 vs. GitHub's Merge Queue

Same idea — serialize landings, test before merge, keep history clean — run
locally instead of in someone else's billed cloud.

🧰 What's in the box

A pre-push hook makes land non-optional: a direct git push straight to
the integration branch is rejected, with the actual command to run
instead, and the same hook runs checkCommand before allowing a landing
through — no checkCommand configured means every push fails by default.
There's a way out for every block (see 🚨 The emergency hatch), but it
takes naming the specific branch, not a generic flag.

📝 What init writes

- claude-code-merge-queue.config.mjs — integrationBranch and checkCommand auto-detected.
- CLAUDE.md (or appends to yours) — tells Claude Code to land its own
  work once green, without being asked.
- .claude/settings.json — the WorktreeCreate hook wired in, without
  touching anything else already there.
- .husky/pre-push — created or appended to, *if* you already have
  Husky. If you don't, init tells…