ENGINEERING
Triage GitLab MR risk and route to the right reviewers in Slack
On MR open, it scores risk from changed paths, diff size, and migration presence, then routes a focused review request to the owning team's Slack channel with the rationale.
How it runs
The automated pipeline, trigger to output.
- TriggerGitLab MR opened webhookGitLab
- ActionFetch changed files and diff statsGitLab
- ActionMap modules and score risk signalsShell
- LogicAssign risk tier and resolve owning team
- OutputRoute review request to team Slack channelSlack
What it does
This workflow decides how much attention a merge request deserves and who should look at it. It combines affected-module mapping with risk signals (diff size, touched migration or auth files, count of crossed modules) into a single risk tier, then sends a targeted review request to the owning team's Slack channel. Low-risk MRs get a quiet ping; high-risk ones get an explicit callout with the reasons.
When to use it
Use it when review load is unevenly distributed and risky changes slip through with the same treatment as trivial ones. It puts the right MR in front of the right people fast.
How it works
- 1A GitLab MR opened webhook fires.
- 2The workflow fetches changed files and diff stats from the GitLab API.
- 3A shell step maps files to modules and computes risk signals.
- 4A logic step assigns a risk tier and resolves the owning team and its Slack channel.
- 5It posts a routed review request to Slack with the risk tier and rationale.
- 6It also posts a short risk note back on the MR for an audit trail.
Set it up
What you configure once, before turning it on.
- 1Connect GitLabRepos, MRs, pipelines, registry.
- 2Connect ShellRun sandboxed commands inside the workspace.
- 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.