Reviews slow down when nobody agrees what to check, so people argue about style and rubber-stamp the rest. This template sets shared checklists for authors and reviewers, with size limits, turnaround targets and an escalation path. It focuses each review on accessibility, performance, component reuse and the styles and tests that keep a frontend healthy.

The sample is for Orchardby Software, a fictional web team that aims for pull requests under 400 changed lines, a first review within four working hours and a median turnaround of five hours. Replace the principles, targets and examples with your own, and keep each checklist short enough that people will actually use it.