An offline, read-only gate for an exported branch snapshot. It evaluates required checks on the current head, approvals, review threads, conflicts and capture age. It never contacts GitHub and cannot assert live queue position.
This walkthrough uses the tool's public README and checked-in example files. Run the command from a repository checkout with Node.js 22+; inspect the source before using it on your own files.
Run the checked-in example
node bin/merge-queue-readiness.mjs --root examples --policy policy.json --snapshot ready.json --at 2026-01-01T00:30:00Z
node bin/merge-queue-readiness.mjs --root examples --policy policy.json --snapshot blocked.json --at 2026-01-01T00:30:00Z
npm run checkRead the result
The first example exits 0; the second exits 1. Inputs are read relative to --root and resolved to real paths within it. Findings use @policy and @snapshot as logical source roles, with JSON pointers into the exact files named at invocation. No content or absolute path from either file is printed.
Where this check stops
This local walkthrough does not establish the state of a live production system or replace the limits documented in the repository.
Before adapting the command to your own workflow, review the accepted inputs, exit codes and safety boundaries in the README.
Compiled with AI assistance from checked-in public documentation and example scripts. Run the example and review the repository's current documentation before relying on its result.