メニュー
Land (queue/merge) a Mergify-managed PR stack safely. Trigger when asked to land, merge, ship, or queue a PR or PR stack with Mergify. Enforces that you act only on SHA-verified PR numbers — never a PR found by branch name.
Codex または Claude でインストール この Prompt をコピーして Codex、Claude、または他のアシスタントに貼り付けると、Skill ページを確認してインストールできます。
SOC 職業分類に基づく
Generate a reusable loop instruction doc, loop driver script, and Invoker workflow from an interview. Trigger: "loop generator", "generate a loop", "invoker-loop-generator", "/invoker-loop-generator", or requests to build a reusable babysit/watch/retry loop. For benchmark/direct-output prompts with "Required output path", write the requested artifact directly to that literal path, do not ask clarifying questions, and do not validate, review-gate, or submit.
Convert a plan into an Invoker YAML plan file. Trigger: "convert to invoker", "submit to invoker", "create invoker plan", "invoker-plan-to-invoker", "/invoker-plan-to-invoker", "/plan-to-invoker", or turning a plan file into Invoker tasks. For benchmark/direct-output prompts with "Required output path", write a complete YAML document directly to that literal path; it must start with top-level name, onFinish, mergeMode, repoUrl, and tasks, never version or metadata wrappers, and must not scan, validate, submit, or discover env vars.
Create or update a pull request in this repo using the preferred PR schema, upstream-first branch workflow, and repo-specific publication rules. Trigger when asked to make a PR, update a PR body, prepare PR text, publish a stacked PR branch, or whenever a branch/PR change means the GitHub PR metadata may now be stale.
Shape code changes, workflow plans, and PR stacks so each diff is easy to review: one local claim, one safety invariant, clear architectural effect, and an explicit reason for the slice.
Get a new machine "good to go" for Invoker and optionally wire up the Slack integration. Trigger when asked to set up Invoker, run the setup/tutorial, check the environment, fix missing tools, or configure the Slack bot ("set up slack", "/setup", "am I good to go?").
Push the current branch and verify it against the CI-equivalent test surface on an available SSH remote target, including selecting a target not currently used by Invoker, creating a temporary remote worktree, and running `pnpm run test:all` with CI-style setup. Use when you need pre-merge confidence that mirrors `.github/workflows/ci.yml` more closely than local-only tests.
| name | land-stack |
| description | Land (queue/merge) a Mergify-managed PR stack safely. Trigger when asked to land, merge, ship, or queue a PR or PR stack with Mergify. Enforces that you act only on SHA-verified PR numbers — never a PR found by branch name. |
Use this skill whenever the user asks to land / merge / ship / queue a PR or a PR stack.
Never identify the PR to land by branch name. Two different PRs can share a
branch name (an auto-generated workflow branch PR and the intended stack/...
PR). You must land by SHA-verified PR number, and every PR must pass the guard
before any write (label, thread-resolve, queue, merge).
Resolve PR numbers, bottom of stack first. If the user gives numbers or URLs, use those. If they do not, make a best-effort read-only discovery pass and suggest the numbers yourself:
gh pr list --state open --json number,baseRefName,headRefName,headRefOid,title --limit 100.headRefName starts with stack/.headRefOid exists in the local clone, so the code
is actually available for review.headRefName.
If they do, present the exact bottom-up PR numbers and ask the user to
confirm them before landing. This is the only discovery case that requires
confirmation.headRefName is unique, run the guard on the suggested
sequence and, when it passes, land it without an additional confirmation.
The requested landing action plus a SHA-verified, guarded PR sequence is
sufficient authorization.Never discover by branch name. Do not run gh pr list --head <branch> to
decide what to land; that is the unsafe path this skill exists to prevent.
Verify with the guard — it must exit 0:
node scripts/land-stack.mjs <bottom-pr> <next-pr> ...
The guard checks, for each PR: head SHA exists in the local clone (it is the
code you reviewed), head branch is a real stack/ branch (rejects raw
workflow branches), the PRs form a proper stack (each base is the previous
head; the bottom's base is the trunk), and all are OPEN. If any check FAILs,
stop and resolve the mismatch with a fresh discovery pass — do not work around it.
Land bottom-up:
node scripts/land-stack.mjs <bottom-pr> ... --execute
This re-verifies, then adds admin-bypass to the bottom PR (base == trunk)
to enter the Mergify queue. Use admin-bypass only because self-authored PRs
cannot be self-approved; if a human can approve, prefer a real approval +
ready-to-merge.
Wait for the bottom PR to merge. Mergify re-runs the full suite on the queued batch (can take ~20 min). When it merges, the next PR auto-re-targets the trunk.
Re-run step 3 with the remaining PR numbers until the stack is landed.
gh pr merge or hand-add admin-bypass to skip the guard.A raw workflow-branch PR (#505) shared a branch name with the intended stack (#2174 / #2175). Landing "the PR on this branch" by name queued the wrong PR. The guard makes that mistake fail closed instead of merging silently.