ENGINEERING
Post test-coverage delta on each GitLab MR
After CI uploads a coverage report, it compares the MR's coverage against the target branch baseline and posts the per-module delta as a merge-request note, flagging any drop.
How it runs
The automated pipeline, trigger to output.
- TriggerGitLab MR pipeline succeeded webhookGitLab
- ActionDownload coverage artifactGitLab
- ActionRead target-branch baselinePostgres
- ActionCompute per-module coverage deltaShell
- LogicClassify improved, flat, or regressed
- OutputPost coverage-delta note on MRGitLab
What it does
This workflow turns raw coverage artifacts into a readable signal on the merge request. When the MR pipeline finishes, it pulls the new coverage report, compares it to the stored baseline for the target branch, and posts a note showing total and per-module coverage deltas. A net decrease is called out explicitly so reviewers don't have to dig through CI logs.
When to use it
Use it when your team wants coverage trends visible inline on the MR rather than buried in pipeline output, and you want a gentle nudge (not a hard gate) when a change reduces coverage.
How it works
- 1A GitLab pipeline-success webhook fires for the MR pipeline.
- 2The workflow downloads the coverage artifact from the pipeline.
- 3It reads the stored target-branch baseline from Postgres (keyed by project and branch).
- 4A shell step computes total and per-module coverage deltas.
- 5A logic step labels the result as improved, flat, or regressed.
- 6It posts the coverage-delta summary as an MR note and updates the baseline when the MR merges.
Set it up
What you configure once, before turning it on.
- 1Connect GitLabRepos, MRs, pipelines, registry.
- 2Connect ShellRun sandboxed commands inside the workspace.
- 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
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.