ENGINEERING
Nudge stale PR reviewers on Slack after SLA breach
Runs on a schedule, finds open GitHub PRs whose requested review has sat untouched past your SLA window.
How it runs
The automated pipeline, trigger to output.
- TriggerSchedule fires every 3 hours during work hours
- ActionList open PRs with pending review requestsGitHub
- LogicKeep only PRs past the review SLA with no review yet
- ActionResolve each reviewer's GitHub login to a Slack userSlack
- OutputDM each stale reviewer the PR link and hours waitedSlack
What it does
Keeps review queues moving by catching pull requests that have been waiting on a specific reviewer longer than your agreed turnaround. Instead of one noisy channel blast, it pings each individual reviewer privately with exactly the PR they're blocking and the elapsed wait time.
When to use it
When your team has a stated review SLA (say, 24 business hours) and PRs routinely stall because a requested reviewer forgot. Best for teams that want gentle, targeted accountability rather than a public shame list.
How it works
- 1A schedule fires every few hours during working hours.
- 2The flow queries GitHub for all open PRs with pending review requests.
- 3A logic step keeps only PRs whose `review_requested` timestamp is older than the SLA threshold and that have no review yet.
- 4For each survivor, it resolves the reviewer's GitHub login to a Slack user.
- 5It sends that reviewer a direct Slack message with the PR title, author, link, and hours waited.
Set it up
What you configure once, before turning it on.
- 1Connect GitHubRepos, issues, pull requests, actions.
- 2Connect SlackChannels, DMs, threads, mentions.
- 3Set each agent's modelWe leave models unset so you pick the tier — fast + cheap, or top-quality.
- 4Tune it to your dataEdit the prompts, filters, and field mappings so it matches how your team works.
- 5Test, then turn it onRun once against a sample, confirm the output, then enable the trigger.
More Engineering workflows
Gate breaking API PRs behind downstream consumer acknowledgement
When a PR introduces a breaking contract change, comments the impact summary back on the PR, applies a blocking label.
Publish a versioned API changelog to Confluence on each release tag
On a new semver release tag, gathers the contract changes since the last release and writes a clean.
Agent reviews model-license fit and suggests compliant swaps on the PR
When a PR adds a Hugging Face model, an agent reads the model card and license, judges fit against your commercial-use policy.
Upgrade Impact Router to Module Code Owners
Maps a dependency-bump PR's affected modules to their CODEOWNERS, then DMs each owner on Slack with only the changelog slice that touches code they own.
Re-Voice IVR Prompts on Phone-Tree Config Merge
When a phone-tree config change merges in GitHub, regenerates the ElevenLabs audio for any prompt whose script changed in the diff and opens a follow-up PR adding the new audio…
Upstream Release to Notion Upgrade Brief
When a watched package publishes a new release, fetches the release notes, maps them to the internal modules that depend on it.
Run it inside a business
This workflow drops into a full company template. Import the org, and this is one of the playbooks its agents run.
Run this workflow in your colony.
14-day trial. No DevOps. No Sales call. Provisioned in under a minute.