All recipes
Engineering View

Pr review digest

Daily PR review queue — high-risk PRs surfaced, stale ones flagged, top reviewers DM'd their personal queues.

Eluu — pr-review-digest
Shown in preview
GitHub Linear Slack
Runtime ~3 min per run
Tokens ~12K per run
Owner an eng lead

Works with

Pick whichever tool your team already uses.

  • Messaging
    Slack Teams
  • PM / Tickets
    Linear Jira Asana
  • Source control
    GitHub GitLab
GitHub
GitHub Pull open PRs
Linear
Linear Score risk + link
Slack
Slack Notify reviewers

What it does

PR review queues grow overnight, and engineers waste 15 minutes every morning figuring out which to look at first. This recipe runs daily, scores every open PR by risk, links it to its Linear ticket, and DMs each reviewer their personal top-5 queue — plus a stale-rollup to eng leads so nothing rots in review.

How it works

  1. Pull PRs. Every open PR across active repos is pulled with review status, requested reviewers, age, and changed-file metadata. Critical-path file changes get detected.
  2. Score risk. Each PR is risk-scored (file criticality × line count × has-tests). PRs are linked to their Linear tickets. Stale (5+ days) and missing-tests-in-critical-path PRs get flagged.
  3. Notify. Each top reviewer gets DM’d their personal top-5 queue; a stale-PR rollup lands in #eng-leads.

Setup

  • Connect a VCS tool (GitHub or GitLab).
  • Connect a PM/tickets tool (Linear, Jira, or Asana).
  • Connect a messaging channel (Slack or Teams).

Variations

  • Run hourly during high-velocity periods (release weeks).
  • Add a “your blocked PRs” digest highlighting reviewer-side blockers.
  • Auto-assign reviewers based on file ownership (CODEOWNERS).