ENGINEERING
Nudge authors when approved PRs aren't merged
Twice a day it finds pull requests that have the required approvals and passing checks but haven't been merged, then DMs the author in Slack to merge or explain the hold.
How it runs
The automated pipeline, trigger to output.
- TriggerTwice-daily schedule
- ActionList open PRs with approvals and check statusGitHub
- LogicFilter to approved, green, past grace window
- ActionDM author in Slack to merge or explainSlack
- OutputPost unmerged-approved digest to team channelSlack
What it does
Approved PRs that sit unmerged quietly pile up technical and coordination debt. This workflow finds PRs that are fully approved with green checks yet still open past a grace window, and nudges the author directly to either merge or say why it's blocked. It keeps the merge queue moving without a human policing it.
When to use it
Use it when your bottleneck isn't getting reviews but actually landing approved work, often because authors forget, are waiting on something undocumented, or fear a Friday merge. Best for teams with required-review branch protection.
How it works
- 1A schedule runs the check twice daily.
- 2The flow lists open PRs and filters to those with all required approvals and passing status checks.
- 3A branch keeps only PRs whose last-approval time is older than the grace window.
- 4For each match it DMs the author in Slack with the PR link, prompting them to merge or post a blocker.
- 5A daily digest of still-unmerged approved PRs is posted to the team channel for visibility.
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.