ENGINEERING
Daily stale-PR escalation ladder
Each morning it scans open pull requests, classifies them by how long they've been waiting.
How it runs
The automated pipeline, trigger to output.
- TriggerWeekday morning schedule
- ActionList open PRs and compute idle timeGitHub
- LogicTier PRs: waiting vs stalled past threshold
- ActionSlack reminder for waiting PRsSlack
- OutputCreate or update Linear escalation issue for stalled PRsLinear
What it does
This runs a daily sweep of all open pull requests and escalates them based on age. Fresh-but-waiting PRs get a gentle Slack nudge to their reviewer. PRs that have sat untouched past a hard threshold get escalated into a tracked Linear issue assigned to the team lead, so they stop slipping through the cracks.
When to use it
Use it when PRs routinely rot for days without a clear owner chasing them, and Slack reminders alone get ignored. Ideal for teams that already track work in Linear and want stalled reviews to become visible, accountable items.
How it works
- 1A scheduled trigger runs every weekday morning.
- 2The flow lists all open PRs and computes each one's hours-since-last-review-activity.
- 3A branch sorts PRs into tiers: waiting 1-2 days versus stalled beyond the escalation threshold.
- 4For waiting PRs it posts a reminder in the team Slack channel tagging the assigned reviewer.
- 5For stalled PRs it creates or updates a Linear issue assigned to the team lead, linking the PR and its idle duration.
Set it up
What you configure once, before turning it on.
- 1Connect GitHubRepos, issues, pull requests, actions.
- 2Connect SlackChannels, DMs, threads, mentions.
- 3Connect LinearIssues, projects, cycles, triage.
- 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.