ENGINEERING
GitLab MR uncovered-diff line annotator
On every GitLab merge request pipeline, compares the new coverage report against the diff and posts inline MR comments on each added or modified line that has no test coverage.
How it runs
The automated pipeline, trigger to output.
- TriggerGitLab MR pipeline succeedsGitLab
- ActionFetch MR diff + coverage artifactGitLab
- LogicCompute uncovered added/modified lines
- LogicSkip files with full coverage
- OutputPost inline comments on uncovered linesGitLab
What it does
Every time a merge request pipeline finishes, this workflow finds the exact lines a developer added or changed and that the test suite never executed, then drops an inline comment on each one inside the MR diff. Reviewers see uncovered code right where it lives instead of digging through a coverage dashboard.
When to use it
Use it when your team wants coverage feedback at review time rather than after merge. It is most valuable for repositories with meaningful suites where untested new logic is the main regression risk, and where you would rather nudge in-thread than block the pipeline.
How it works
- 1A GitLab pipeline-success webhook fires for a merge request pipeline.
- 2The flow fetches the MR diff and the pipeline's Cobertura/LCOV coverage artifact from GitLab.
- 3It intersects added/modified line numbers per file with the set of executed lines, producing the uncovered-diff set.
- 4A logic step skips files with zero uncovered diff lines.
- 5For each remaining line it posts an inline discussion on the MR, then writes one summary note listing total uncovered new lines.
Set it up
What you configure once, before turning it on.
- 1Connect GitLabRepos, MRs, pipelines, registry.
- 2Set each agent's modelWe leave models unset so you pick the tier — fast + cheap, or top-quality.
- 3Tune it to your dataEdit the prompts, filters, and field mappings so it matches how your team works.
- 4Test, 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.