1 / 5
A reviewer writes: 'This PR is too large to review effectively — could you split it?' What is the underlying concern?
-
-
-
-
Big PRs reduce review quality; smaller, focused diffs are easier to reason about.
2 / 5
What are 'stacked PRs'?
-
-
-
-
Stacked (chained) PRs break a big change into a sequence of small, dependent reviews.
3 / 5
A reviewer says: 'Let's scope this PR to the API change and move the UI work to a follow-up.' What does 'scope' mean?
-
-
-
-
Scoping a PR limits it to one logical change, deferring unrelated work to a follow-up.
4 / 5
Which phrase appropriately requests a smaller change?
-
-
-
-
Suggesting the author split unrelated work keeps each PR focused and reviewable.
5 / 5
A reviewer does a 'high-level pass' first. What does that mean?
-
-
-
-
A high-level pass evaluates architecture and approach before drilling into line-level details.