pr-small-cl

Split a large pull request by choosing seams that give each increment a coherent purpose and test boundary. Common approaches include separating preparation refactors from behavior changes, splitting independent vertical features, or stacking changes where each builds on a stable foundation.

A reviewable pull request delivers one coherent outcome with its implementation, tests, documentation, and configuration. A reviewer should be able to understand the change with its context and verification, and the system should remain in a usable state.

Ask for a split when the change's breadth prevents a reliable assessment of design, behavior, or verification. Identify the first coherent increment and the remaining increments so the author has an actionable path forward.

Stacked pull requests are a splitting strategy where each earlier change supplies the next change's stable foundation. Use them when increments depend on each other sequentially, and state the dependencies between related pull requests explicitly.

Keep each increment safe by ensuring it leaves the system in a usable state and can be merged or reverted on its own. Each split should have a clear test boundary and include the tests and documentation needed for its outcome.