PR slices make review and recovery smaller
A PR slice is a coherent unit of change with one purpose, its own checks, and a clear boundary. Splitting by arbitrary file count is less useful than splitting by behavior or decision.
Small slices make it easier to review, revert, or resume after interruption.
| Slice | Example purpose |
|---|---|
| Regression slice | Add a failing or characterization check |
| Fix slice | Make the smallest behavior change |
| Documentation slice | Update the contract and handoff |
| Follow-up slice | Separate optional cleanup or later risk |
Slice checklist
- Name one purpose per slice.
- Keep related tests with the behavior they protect.
- Avoid mixing formatting or unrelated refactoring.
- Run focused checks before opening the next slice.
- Record dependencies between slices.
- Review the combined result before merge.
PR slicing note
PR 1: characterization/regression evidence
PR 2: minimal implementation change
PR 3: docs and handoff
Dependency: PR 2 waits for PR 1
Decision: keep optional cleanup outside this taskCanonical lesson source · JavaRush
Open JavaRush material