Back to Cookbook
PR Review SLA Enforcer
Keep reviews from becoming the bottleneck
Reduce PR queue time with clear SLAs, review routing, and "what's blocking merge" visibility — without turning review into bureaucracy.
CommunitySubmitted by CommunityWork15 min
INGREDIENTS
🐙GitHub💬Slack
PROMPT
Create a skill called "PR Review SLA Enforcer". The skill must: - Generate a PR review policy (SLA, routing, escalation) - Produce a PR template that enforces context and test evidence - Define "blocking vs non-blocking" review guidance - Recommend metrics to track (review latency, re-review cycles) Output as a policy draft plus a PR template.
How It Works
This recipe introduces review hygiene: small PRs, explicit blocking vs non-blocking feedback,
and escalation when reviews exceed the agreed SLA.
Triggers
- PRs wait days for reviews
- Review comments are ambiguous ("is this blocking?")
- Teams complain that review, not coding, is the bottleneck
Steps
- Establish review SLAs (e.g., first response within 4 business hours).
- Use a PR template that forces context: why, risk, test evidence.
- Require reviewers to mark comments as blocking or non-blocking.
- Escalate stale reviews (auto ping; then rotate to a backup reviewer).
- Track review latency metrics and address chronic bottlenecks.
Expected Outcome
- Faster merges and fewer stalled PRs.
- Reduced bikeshedding and clearer decision-making.
Example Inputs
- "We need reviews same-day for most PRs."
- "People leave comments but don't approve or block."
- "Large PRs are hard to review and cause slowdowns."
Tips
- Review is coordination work: make the state unambiguous.
Tags:#code-review#developer-productivity#onboarding#documentation