Stacked PRs Manager FAQs

Question 1

When should I use stacked PRs instead of independent PRs?

Accepted Answer

Use stacked PRs when your changes build sequentially on top of unmerged work. Use independent PRs when changes are self-contained and can be merged in any order.

Question 2

Does this skill help with PR reviewability?

Accepted Answer

Yes, it follows 'Small CL' principles to help you split changes by type (e.g., refactoring vs. feature) or file group, ensuring each PR is roughly 100 lines and easily reviewable.

Question 3

How do I update the stack after the first PR is merged?

Accepted Answer

The skill guides you to fetch main, merge it into the original branch, and then perform sequential merges into each downstream branch (pr2, pr3, etc.) to maintain synchronization.

Question 4

What are stacked PRs?

Accepted Answer

Stacked PRs are a chain of pull requests where each branch builds on the previous one, allowing for smaller, more focused reviews of large features that have internal dependencies.

Question 5

How does this skill handle merge conflicts?

Accepted Answer

It implements a 'cascade merge' strategy: it merges main into the base branch first, then propagates those changes downstream one branch at a time to isolate and simplify conflict resolution.

Stacked PRs Manager

主な機能

ユースケース

Stacked PRs Manager

主な機能

ユースケース