land-stack

Lands Mergify-managed PR stacks by SHA-verified PR numbers with a guard script.

18|5|Updated Apr 17, 2026
One-click install
npx skills add https://github.com/Neko-Catpital-Labs/Invoker --skill land-stack-neko-catpital-labs
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: land-stack
Source: https://github.com/Neko-Catpital-Labs/Invoker/tree/main/skills/land-stack
Command: npx skills add https://github.com/Neko-Catpital-Labs/Invoker --skill land-stack-neko-catpital-labs

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) components.

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.

Frequently Asked Questions about land-stack

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

FAQPage Schema
How do I merge a stacked PR series with Mergify?

Resolve the PR numbers bottom-up, run the guard script to verify SHAs and stack order, then execute the landing script which adds admin-bypass to the bottom PR to enter the Mergify queue. Repeat with remaining PRs after each merge.

Why should I not look up a PR by branch name before merging?

Two different PRs can share the same branch name, such as an auto-generated workflow branch PR and the intended stack PR. Landing by branch name can queue the wrong PR, so this Skill requires SHA-verified PR numbers instead.

What does the land-stack guard script check?

The guard verifies each PR's head SHA exists in the local clone, the head branch is a real stack/ branch, the PRs form a proper stack with each base matching the previous head, and all PRs are OPEN. Any failure stops the landing.

When is user confirmation required before landing a stack?

Confirmation is required only when discovery finds two or more open PR candidates sharing the same headRefName. If all candidate branch names are unique and the guard passes, the stack lands without extra confirmation.

Why use admin-bypass instead of a normal approval to queue a PR?

Self-authored PRs cannot be self-approved on GitHub, so admin-bypass is used to enter the Mergify queue. When a human reviewer is available, a real approval plus the ready-to-merge label is preferred.