What problem does it solve? Landing a pull request on a repo that uses GitHub's native merge queue involves more than clicking merge: automerge must be enabled, CI must pass on the queue branch, and stacked PRs risk merging into their parent's feature branch instead of main. This Skill automates the entire flow and watches until the PR actually merges. ## Core Features & Use Cases - Automerge and monitoring: Enables automerge on PRs targeting main and polls until the PR actually merges, reporting CI failures, conflicts, or queue removal. - Stacked PR handling: Detects PRs targeting a feature branch, waits for the parent PR to merge, retargets the child to main, then enables automerge automatically. - Failure recovery guidance: Reports terminal failure states (CI failure, merge conflict, closed parent, unmergeable queue entry) with instructions to fix and rerun. - Use Case: You open PR #42 stacked on PR #41. Run the land script once; a background watcher waits for #41 to merge, retargets #42 to main, enqueues it, and notifies you when it lands. ## Quick Start Ask the assistant to land PR number 42 using the landing-prs skill and watch it until it merges.