chained-pr

To split a large pull request, you decompose oversized code changes into sequential, reviewable slices using stacked PRs or feature branch chains. This maintains code quality and review velocity for diffs exceeding 400 lines.

Managing code review fatigue requires enforcing strict line-count limits to keep every pull request within a 60-minute review budget. Slicing complex refactoring tasks into logical, independent units ensures clear review history.

You need stacked PRs when implementing complex feature development or refactoring tasks where diffs exceed 400 lines. This strategy maintains CI health and tracks dependencies for multi-PR features.

Tracking dependencies across sequential pull requests involves maintaining clear dependency diagrams and updating PR templates. This ensures atomic delivery and logical ordering for complex multi-PR features.

Yes, you can use chained PRs for a 1000 line refactor by asking the agent to analyze the branch and propose a strategy. It slices the work into independent units to maintain CI health and clear review history.

Enforcing a 60-minute review budget requires strict line-count limits, meaning oversized changes must be manually decomposed. This limits atomic delivery of large features without proper branching strategies and dependency tracking.