ENGINEERING
Weekly GitLab review-load fairness digest
Once a week, computes per-reviewer review volume, turnaround time, and current backlog from the assignment ledger.
How it runs
The automated pipeline, trigger to output.
- TriggerWeekly schedule
- ActionAggregate per-reviewer stats from ledgerPostgres
- LogicRank reviewers and flag overload
- ActionEnrich flagged entries with open MR titlesGitLab
- OutputPost fairness digest to SlackSlack
What it does
This workflow turns the raw assignment history into a weekly leaderboard. It aggregates how many MRs each reviewer handled, their median time-to-first-review, and how deep their current backlog is, then renders a clear digest that highlights who is overloaded and who has spare capacity.
When to use it
Use it when you want a recurring, data-backed view of review fairness rather than gut feel. It is ideal for an engineering manager who runs weekly health checks and wants the numbers handed to them automatically.
How it works
- 1A weekly schedule trigger fires at a set time.
- 2The workflow queries Postgres for assignment counts, turnaround times, and open backlog per reviewer over the trailing seven days.
- 3A logic step ranks reviewers and flags anyone above the overload threshold or with stale backlog.
- 4It pulls current open-MR titles from GitLab to enrich the flagged entries.
- 5It formats a ranked digest with per-person stats and callouts.
- 6The digest posts to the engineering-leads Slack channel.
Set it up
What you configure once, before turning it on.
- 1Connect PostgresAny Postgres URL — query, write, migrate.
- 2Connect GitLabRepos, MRs, pipelines, registry.
- 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.
