ENGINEERING
GitLab MR coverage-regression gate and labeler
Compares an MR's project coverage percentage against the target branch baseline and, when coverage drops beyond a threshold, applies a coverage-regression label and posts…
How it runs
The automated pipeline, trigger to output.
- TriggerGitLab MR pipeline succeedsGitLab
- ActionRead MR total coverageGitLab
- ActionLook up target-branch baselinePostgres
- LogicCompare delta vs threshold
- ActionAdd or clear regression labelGitLab
- OutputUpsert new branch baselinePostgres
What it does
This workflow reads the total coverage percentage produced by a merge request pipeline and compares it to the most recent coverage recorded on the target branch. If the MR lowers coverage by more than your allowed delta, it labels the MR `coverage-regression` and posts a note explaining the drop; if it improves or holds, it clears the label.
When to use it
Use it when you enforce a coverage ratchet and want a visible, queryable signal on MRs rather than a hard pipeline failure. The label lets you filter the MR board and configure GitLab merge rules around it without editing CI scripts per project.
How it works
- 1A GitLab MR pipeline-success webhook triggers the flow.
- 2It reads the MR's total coverage from the GitLab pipeline coverage field.
- 3It looks up the stored baseline coverage for the target branch in Postgres.
- 4A logic step computes the delta against the allowed threshold.
- 5On a regression it adds the `coverage-regression` label and posts a note; otherwise it removes the label.
- 6It upserts the new branch baseline into Postgres for the next comparison.
Set it up
What you configure once, before turning it on.
- 1Connect GitLabRepos, MRs, pipelines, registry.
- 2Connect PostgresAny Postgres URL — query, write, migrate.
- 3Set each agent's modelWe leave models unset so you pick the tier — fast + cheap, or top-quality.
- 4Tune it to your dataEdit the prompts, filters, and field mappings so it matches how your team works.
- 5Test, 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.