ENGINEERING
Escalate GitLab MRs with no available code owner
When an MR opens but every matching code owner is over capacity or unavailable, escalates to a fallback reviewer pool and opens a Linear task flagging the ownership gap.
How it runs
The automated pipeline, trigger to output.
- TriggerGitLab MR opened or readyGitLab
- ActionCheck owner availability and limitsPostgres
- LogicBranch when no owner is available
- ActionAssign lightest fallback-pool reviewerGitLab
- ActionOpen ownership-gap Linear taskLinear
- OutputAlert leads in SlackSlack
What it does
This workflow handles the edge case the simple balancer can't: an MR whose code owners are all over their queue limit, on leave, or missing entirely. Instead of silently leaving it unassigned, it routes the MR to a configured fallback pool and files a Linear task so the team can fix the underlying ownership or staffing gap.
When to use it
Use it alongside your primary reviewer-assignment workflow as a safety net. It surfaces structural problems, like a module with only one overloaded owner, that would otherwise show up as mysteriously stalled MRs.
How it works
- 1A GitLab webhook fires when an MR is opened or ready.
- 2The workflow resolves code owners and checks each against their queue limit and availability in Postgres.
- 3A logic step branches: if at least one owner is available it exits to the normal path; otherwise it escalates.
- 4On escalation it assigns the lightest member of the fallback pool via GitLab.
- 5It opens a Linear task tagged ownership-gap with the module and the owners who were unavailable.
- 6It alerts the engineering-leads Slack channel that a gap was hit.
Set it up
What you configure once, before turning it on.
- 1Connect GitLabRepos, MRs, pipelines, registry.
- 2Connect PostgresAny Postgres URL — query, write, migrate.
- 3Connect LinearIssues, projects, cycles, triage.
- 4Connect SlackChannels, DMs, threads, mentions.
- 5Set each agent's modelWe leave models unset so you pick the tier — fast + cheap, or top-quality.
- 6Tune it to your dataEdit the prompts, filters, and field mappings so it matches how your team works.
- 7Test, then turn it onRun once against a sample, confirm the output, then enable the trigger.
More Engineering workflows
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.
Block PRs that add incompatible Hugging Face model licenses
When a pull request adds or bumps a Hugging Face model dependency, it fetches the model card license, checks it against your org's allowed-license policy.
Quarterly Logging Hygiene Audit Agent
An agent-driven quarterly sweep that surveys all Axiom datasets, builds a logging-hygiene scorecard per service.
Post-Merge Log Volume Recheck After Downsampling PR
After a log-level PR merges, waits a day then re-queries Axiom to confirm the targeted stream's volume actually dropped.
Axiom Ingest Cost Spike to Linear Triage Ticket
When Axiom ingest volume spikes beyond its baseline, identifies which service caused it and files a Linear ticket with the offending log stream, sample lines, and a downsampling…
File a Linear license-review ticket for risky model adds
When a PR introduces a Hugging Face model with a non-permissive or unknown license, it opens a Linear issue assigned to the legal-review team with the model, license.
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.