What problem does it solve? Managing stacked pull requests manually with git rebase and gh commands is error-prone: PR titles drift from commit messages, interactive rebases hang in agent sessions, and fix commits create unwanted extra PRs. This Skill enforces a consistent stacked-PR workflow where every commit maps to one PR and the entire PR lifecycle is driven by commit messages. ## Core Features & Use Cases - Stacked PR creation and sync: Use mergify stack push to turn local commits into stacked PRs, mergify stack sync to rebase onto trunk and drop merged commits, and mergify stack list to inspect commit-to-PR mapping with CI and review status. - Non-interactive history rewriting: Reorder, move, fixup, squash, reword, edit, and drop commits with dedicated mergify stack subcommands instead of git rebase -i, which hangs in agent contexts. - Amend notes and revision history: Attach mergify stack note reasons before pushing so reviewers see why a commit was amended in the PR's revision history. - Use Case: You need to fix a lint error in the middle of a five-commit stack. Stash changes, run mergify stack edit <SHA>, amend the commit, continue the rebase, add a note explaining the fix, and push — all PRs update in place. ## Quick Start Check the current branch with git, create a new stack with mergify stack new feat/my-change, commit your work, then run mergify stack push to create the stacked pull requests.
