Stacked Pull Requests

Stacked pull requests break complex features into smaller, dependent branches, simplifying review and integration. You create a sequence of dependent branches, starting with a base feature branch and stacking subsequent branches on top of the previous ones.

Branch naming conventions for stacked PRs typically use a sequential numbering scheme to indicate dependency order. For example, you name branches sequentially like 'feature/001-base', 'feature/002-dependency', and 'feature/003-next' to clearly define the stack hierarchy.

Rebasing and merging dependent branches requires updating the base of each child branch sequentially after the parent merges. This Skill provides specific strategies for rebasing dependent branches to ensure your pull request stack remains intact throughout the integration process.

Common pitfalls include branch misalignment and improper dependency tracking during rebases. This Skill addresses these by providing PR description templates to explicitly declare dependencies and agent instructions for automating the workflow to prevent integration errors.

Use stacked pull requests when developing complex features that require phased development, such as building an authentication system followed by dependent user profile and admin panels. This allows reviewers to focus on incremental changes rather than a massive codebase.

Yes, this Skill provides agent instructions for automating the stacked PR workflow. It guides the process of creating sequential dependent branches, applying naming conventions, and generating PR description templates to streamline automated feature integration.