ENGINEERING
Reassign stale GitLab reviews on a schedule
On a recurring schedule, finds merge requests whose assigned reviewer has gone quiet past an SLA window and reassigns them to the next-lightest code owner.
How it runs
The automated pipeline, trigger to output.
- TriggerScheduled sweep every few hours
- ActionList open MRs and last review activityGitLab
- LogicKeep MRs idle past SLA window
- ActionRank alternate owners by queue depthPostgres
- ActionReassign MR and update ledgerGitLab
- OutputNotify new and prior reviewers in SlackSlack
What it does
This workflow runs on a timer, scans every open merge request, and flags any where the assigned reviewer has not commented, approved, or requested changes within your SLA window. For each stale MR it rebalances the work to a different eligible owner with a lighter load and notifies everyone involved.
When to use it
Run it when reviews routinely stall because a reviewer went on leave, got pulled onto an incident, or simply lost the thread. It recovers blocked MRs without an engineering manager manually auditing the board.
How it works
- 1A schedule trigger fires every few hours during working hours.
- 2The workflow lists open MRs from GitLab and reads the last review activity timestamp on each.
- 3A logic step keeps only MRs idle longer than the configured SLA.
- 4For each stale MR it queries Postgres for alternate code owners ranked by current queue depth.
- 5It reassigns the MR to the lightest alternate via GitLab and updates the assignment ledger.
- 6Slack pings the new reviewer with the MR and DMs the prior reviewer a heads-up that it was handed off.
Set it up
What you configure once, before turning it on.
- 1Connect GitLabRepos, MRs, pipelines, registry.
- 2Connect PostgresAny Postgres URL — query, write, migrate.
- 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
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…
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.
Scan for deprecated endpoints and email consumers a weekly sunset countdown
On a weekly schedule, scans the OpenAPI spec for endpoints marked deprecated with a sunset date, and emails each consuming team a countdown of how many days remain before removal.
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.
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.
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.