branch-surgery-pr-split

To split a large git branch into smaller pull requests, you decompose the oversized branch into a stack of focused PRs using safety refs and topology selection. This reduces review burden and prevents merge conflicts without losing net changes.

Breaking down a mixed-concern pull request for code review involves decomposing the monolithic branch into separate, focused PRs. The process uses topology selection, such as stacked or fan-out branching, to isolate features, bug fixes, and documentation updates.

Branch decomposition prevents losing changes during git refactoring by implementing rigorous audit gates and safety refs. These mechanisms ensure that all changes from the original oversized branch are accurately attributed and preserved across the new PR stack.

You need to use stacked PRs instead of a single pull request when your branch becomes oversized, mixed-concern, or prone to conflicts. Decomposing the branch into a stack makes the code review process significantly more manageable and safer.

Available topology patterns for branching and PR stacking include stacked and fan-out configurations. The skill uses references to guide topology selection, ensuring the branching strategy matches the specific merge sequencing and review needs of your decomposed branch.

Yes, you can use branch surgery to separate feature updates from bug fixes in one workflow. The skill decomposes mixed-concern branches into multiple focused PRs, applying merge sequencing to safely isolate and review each distinct concern.