Synthesis Review Triage

Review triage decides which PR to review next. It does not evaluate code — that is the job of synthesis-pr-review and synthesis-code-audit. Triage is a routing and scheduling methodology: classify the queue, score each item by urgency, and direct review effort where it has the most impact.

Binding rules

1. Triage is routing, not evaluation. Do not assess code quality during triage. That is what pr-review and code-audit are for.
2. The scoring is a framework, not a formula. Adapt weights to your team's context. A team with a strict SLA on review turnaround might weight age higher. A team with frequent CI flakiness might weight CI status lower.
3. Author-response detection prevents misclassification. Always check for post-review commits before labeling a PR as "waiting on author."
4. "Already reviewed" does not mean "already approved." Distinguish carefully — a commented review with no verdict is not a completed review.
5. Respect explicit team signals. Priority labels, blocker tags, and team conventions override the scoring framework.
6. Exclude before scoring: your own PRs, drafts, PRs you already approved, and PRs you reviewed with no code commits since.
7. Review in tier order; within a tier, the scoring dimensions break ties. Priority labels override the scores.
8. Before re-reviewing a PR you already reviewed, run the prior-review gate and choose full, delta or skip; a rebase alone rarely earns a full review.

Contents