What problem does it solve? Large changes crammed into a single pull request stall reviews and make feedback hard to track. This Skill helps you decide whether a change should be split before you start, split it into branches, and organize the resulting PRs as a dependency stack on GitHub. ## Core Features & Use Cases - Split Decision Criteria: Judges whether to split based on whether a reviewer can read the change in one pass, not on file independence, with concrete signals like multiple purposes or growing file counts. - Dependency Verification: Uses git diff, merge-base, and merge-tree to determine real merge-order dependencies between PRs, including the special case of lint/type-check PRs that depend on all others. - Stack Management with gh stack: Adopts branches bottom-up with gh stack init, pushes and links with gh stack submit --auto, and retroactively stacks already-opened PRs with gh stack link without touching PR bodies or review comments. - Use Case: You realize mid-feature that your branch mixes a refactor and a new feature. Use this Skill to split them into two branches, stack them with gh stack, and annotate each PR with its merge order. ## Quick Start Ask the assistant to evaluate whether your current branch should be split into a stacked set of PRs and set up the stack with gh stack.
