Score breakdown
Popularity is tracked separately. Support, ads, sponsorships, and tips never affect these signals.
Why it matters
Useful for AI-coding power users, agent developers, engineering teams, DevOps engineers, SREs, engineering managers, AI-curious readers, founder-CTOs, automation builders, and any developer who runs multiple Claude Code agents in parallel against the same branch and wants the collision surface to be impossible rather than asked-nicely. The durable differentiator is that Claude Code's --worktree (o
Who should use it
Who should skip it
Consider funador/claude-code-merge-queue lower priority if you already have a working solution in this category.
About this signal
funador/claude-code-merge-queue is tracked by RepoRadar as a local zero-cost merge queue for in the Developer Tooling / Claude Code Plugin section. It was first seen on 2026-07-06 and last updated on 2026-07-06. The current verdict is 'try now' with a Gold tier and easy setup difficulty. The standout signals for funador/claude-code-merge-queue are workflow potential (9.7) and practical usefulness (9.0), while maturity (6.5) trails — that balance shapes where it fits best. This page summarizes the evidence RepoRadar has captured from captured source metadata. The score, tier, risk label, and verdict on this page are never influenced by sponsorship, ads, or tips — they reflect only the usefulness, popularity, novelty, momentum, maturity, and evidence signals described in the RepoRadar methodology.
How this item is evaluated
RepoRadar assigned funador/claude-code-merge-queue a composite score of 8.2 out of 10, placing it in the Gold tier. This score combines weighted sub-signals: usefulness (35%), novelty (18%), momentum (14%), maturity (10%), open-source/build quality (7%), evidence quality (6%), workflow potential (6%), and setup ease (4%). Popularity is tracked separately at 1.0 and never affects the composite score or tier. The risk label of 'low' reflects inherent user-impacting hazards, not generic novelty. Items with no risk flag may still require normal code review before production use.
Putting this into practice? Read How to evaluate an AI tool before you adopt it for the checklist behind this score.
Risk explanation
The 295★ / 433KB TypeScript codebase is very recent (created 2026-07-02; 4 days before this cycle) and the community is small -- treat the first evaluation cycle as a smoke test (npm install + npx init + commit the surface + run two parallel Claude Code worktree sessions against the same integration branch) before relying on the auto-install CLAUDE.md block in production; the project has renamed once already (lanekeeper -> claude-code-merge-queue) and the README explicitly calls out that future renames are possible -- the preflight safety-net script is the durable mitigation; but pin the npm version in package.json and audit the preflight output on every install.