MR Buddy

Split an oversized MR into a stacked chain of small MRs, each a vertical slice — one capability cutting through all layers (code + tests + docs), reviewable and verifiable alone. Reviewer sees one increment per MR; merge order = review order.

The stack: slice-1 → target, slice-2 → slice-1 … Slice 1 lives on the original MR's branch (the original MR shrinks to the first slice, its history is never lost); slices 2..N are new branches, each targeting the previous slice's branch.

Process

Step 1: Gather the MR's shape

Given an MR URL/iid or a feature branch + target: