ENGINEERING
Track GitLab review assignments as Linear tasks
When a reviewer is assigned to a merge request, creates or updates a Linear review task on that reviewer so review work shows up alongside their feature load in sprint planning.
How it runs
The automated pipeline, trigger to output.
- TriggerGitLab reviewer-assigned or MR-closed eventGitLab
- LogicRoute by event type
- ActionLook up reviewer queue depth for priorityPostgres
- ActionCreate or update Linear review taskLinear
- OutputComplete Linear task on MR closeLinear
What it does
This workflow makes review work visible in your sprint board. Whenever GitLab assigns a reviewer, it opens a lightweight Linear task assigned to that engineer, linked to the MR. When the MR merges or closes, it marks the matching Linear task done, so review effort is planned and accounted for instead of being invisible overhead.
When to use it
Use it when your team plans capacity in Linear but reviews never appear there, leaving reviewers silently overcommitted. It gives leads an honest picture of who is buried in review work.
How it works
- 1A GitLab webhook fires on reviewer-assigned and MR-closed events.
- 2A logic step routes assigned events to create-or-update and closed events to completion.
- 3For an assignment, it looks up the reviewer's queue depth in Postgres to set task priority.
- 4It creates or updates a Linear task on that reviewer with the MR link and priority.
- 5For a close event, it finds the linked Linear task and transitions it to Done.
- 6It writes the task ID back to Postgres so future events resolve the same task.
Set it up
What you configure once, before turning it on.
- 1Connect GitLabRepos, MRs, pipelines, registry.
- 2Connect LinearIssues, projects, cycles, triage.
- 3Connect PostgresAny Postgres URL — query, write, migrate.
- 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.