ENGINEERING
GitLab MR Pipeline Slowdown Reviewer Comment
On each merge-request pipeline, compares its duration to the target branch's recent baseline and, if this MR's changes slowed CI, posts a GitLab comment on the MR naming…
How it runs
The automated pipeline, trigger to output.
- TriggerGitLab merge-request pipeline finishedGitLab
- ActionFetch target-branch baseline pipelinesGitLab
- LogicDetect MR-introduced slowdown; stop if clean
- ActionBisect stage that grew most under the MRGitLab
- OutputComment regression evidence on the MRGitLab
What it does
It shifts CI-duration regressions left to the merge request. When an MR pipeline finishes, it compares that run against the target branch's recent baseline. If the MR's changes made the pipeline slower, it bisects to the responsible stage and leaves a comment on the MR itself, so the author sees the cost of their change before it lands.
When to use it
Use it when slow CI regressions keep slipping into main because nobody reviews pipeline timing during code review. This puts the regression evidence right in the MR thread, making it part of the merge conversation instead of a post-merge surprise.
How it works
- 1A GitLab pipeline webhook fires for a merge-request pipeline.
- 2The flow fetches recent target-branch pipelines to establish the expected duration.
- 3A logic step checks whether the MR run exceeds the baseline beyond the allowed margin; clean MRs stop here.
- 4It bisects per-job timings to the stage that grew most under this MR.
- 5A comment is posted on the merge request naming the stage, the delta, and a suggestion to investigate before merging.
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
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.