Stack Pull Requests

Decide whether planned vertical implementation work should ship as independent pull requests or as a stack of small ordered pull requests, then plan, build, review, update, and merge the stack safely. Use when one slice is too large for effective review, when later slices should proceed on the same evolving baseline before earlier pull requests merge, when AI-generated code volume needs deliberate review boundaries, when a plan already defines dependent pull request boundaries or non-trunk bases, or when the user mentions stacked PRs, PR stacks, dependent PRs, gh-stack, bottom-up review, or splitting an implementation across branches. Do not use this skill to split epics or invent horizontal backlog stories; use story-splitting first.

citypaul Updated 760 repo stars
Watch me use my CLAUDE.md file to build a real feature

File contents

citypaul/.dotfiles commit b71b5a73e0

Frequently asked questions

npx get-skill add citypaul/stack-pull-requests