ENGINEERING
Escalate severely stale PRs to Linear and ping the manager
When an open PR has waited past a hard escalation threshold, it opens (or updates) a Linear issue tracking the blocked review and notifies the reviewer's manager on Slack…
How it runs
The automated pipeline, trigger to output.
- TriggerSchedule runs several times daily
- ActionFetch open PRs and pending-review durationsGitHub
- LogicIsolate PRs past the hard escalation threshold
- ActionCreate or update a Linear issue for the blocked reviewLinear
- OutputSlack the reviewer's manager with PR and issue linksSlack
What it does
Handles the PRs that slipped past gentle reminders. Once a review has been blocked beyond a hard limit, this creates a tracked Linear issue so the stall is visible in your normal planning workflow, and it escalates to the reviewer's manager rather than re-pinging the reviewer who already ignored the nudge.
When to use it
As the second tier behind a soft-reminder workflow. Use it when a missed review starts blocking releases or other engineers and needs management visibility, not just another DM.
How it works
- 1A schedule runs a few times a day.
- 2The flow fetches open PRs and their pending-review durations from GitHub.
- 3A logic step isolates PRs past the hard escalation threshold.
- 4For each, it creates a Linear issue (or updates the existing one) describing the blocked review, reviewer, and elapsed time.
- 5It looks up the reviewer's manager and sends them a Slack message linking the PR and the Linear issue.
Set it up
What you configure once, before turning it on.
- 1Connect GitHubRepos, issues, pull requests, actions.
- 2Connect LinearIssues, projects, cycles, triage.
- 3Connect SlackChannels, DMs, threads, mentions.
- 4Set each agent's modelWe leave models unset so you pick the tier — fast + cheap, or top-quality.
- 5Tune it to your dataEdit the prompts, filters, and field mappings so it matches how your team works.
- 6Test, 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.