ENGINEERING

Nudge reviewers on PRs stuck waiting for review

Every few hours, finds open GitHub PRs that have sat without a review past your SLA and DMs the assigned reviewers in Slack with a direct link.

CategoryEngineering
Enginesim
Difficultybeginner
Triggerschedule
Steps5
Setup~5 min

How it runs

The automated pipeline, trigger to output.

  • TriggerEvery 3 hours during work hours
  • ActionList open PRs across reposGitHubGitHub
  • LogicKeep PRs past review SLA with no review yet
  • ActionResolve requested reviewers to Slack usersGitHubGitHub
  • OutputDM each reviewer the stale PR linkSlack

What it does

Scans your repositories for open pull requests that have been waiting on review longer than a threshold you set (for example, 8 working hours), then sends a focused Slack direct message to each requested reviewer with the PR title, age, and a one-click link. It only pings reviewers who have not yet submitted a review, so it never nags people who are already done.

When to use it

When PRs routinely stall because a review request gets buried in notifications. Good for teams with a review SLA who want gentle, automated follow-up instead of public call-outs in a busy channel.

How it works

  1. 1A schedule fires every few hours during working hours.
  2. 2The workflow lists open PRs across the configured repos via the GitHub API.
  3. 3A filter keeps only PRs whose review was requested more than the SLA threshold ago and that still have no submitted review.
  4. 4For each remaining PR it resolves the requested reviewers and maps GitHub handles to Slack users.
  5. 5It sends each reviewer a private Slack DM with the PR link and how long it has been waiting.

Set it up

What you configure once, before turning it on.

  1. 1
    Connect GitHubRepos, issues, pull requests, actions.
  2. 2
    Connect SlackChannels, DMs, threads, mentions.
  3. 3
    Set each agent's modelWe leave models unset so you pick the tier — fast + cheap, or top-quality.
  4. 4
    Tune it to your dataEdit the prompts, filters, and field mappings so it matches how your team works.
  5. 5
    Test, then turn it onRun once against a sample, confirm the output, then enable the trigger.

Run this workflow in your colony.

14-day trial. No DevOps. No Sales call. Provisioned in under a minute.