What problem does it solve? Landing a stacked pull request series through Mergify is error-prone: two PRs can share a branch name, and acting on the wrong one silently queues unintended code. This Skill enforces landing only by SHA-verified PR numbers, so the exact reviewed code is what gets merged. ## Core Features & Use Cases - SHA-Verified Guard: Runs scripts/land-stack.mjs to confirm each PR's head SHA exists locally, branches are real stack/ branches, the PRs form a proper stack, and all are OPEN before any write. - Safe Discovery: Enumerates open PRs read-only, orders them bottom-up by base/head links, and requires confirmation only when duplicate branch names are detected. - Bottom-Up Landing: Adds admin-bypass to the bottom PR to enter the Mergify queue, waits for merge, then repeats with remaining PRs. - Use Case: You have a three-PR stack (#2174, #2175, #2180) managed by Mergify. The Skill verifies the chain, queues the bottom PR, waits for it to merge, and lands the rest in order. ## Quick Start Ask the assistant to land or merge your Mergify PR stack, optionally providing the PR numbers in bottom-up order.