ENGINEERING
Auto-Quarantine MR for Persistent Flaky Specs
For tests that stay flaky past a grace period, an agent opens a GitLab merge request that applies a skip/quarantine annotation to the spec, links the tracking issue.
How it runs
The automated pipeline, trigger to output.
- TriggerDaily schedule
- ActionList stale flaky::quarantine issues past grace periodGitLab
- LogicLocate failing spec and choose skip annotation
- ActionEdit test file and open quarantine MRGitLab
- OutputAssign code owner and link issue to the MRGitLab
What it does
Takes flaky tests that have been flagged but unaddressed beyond a grace period and actually proposes the fix: an agent edits the test file to add the appropriate quarantine annotation for your framework, opens a merge request, links the existing tracking issue, and requests review from the spec's code owner.
When to use it
Use it when quarantine issues pile up but nobody gets around to silencing the tests, so the same flaky specs keep poisoning unrelated pipelines. This closes the loop with a reviewable change rather than auto-merging anything.
How it works
- 1A daily schedule trigger fires.
- 2The agent queries GitLab for `flaky::quarantine` issues older than the grace period (default 5 days).
- 3For each, it reads the referenced test file, locates the failing spec, and applies the framework-correct skip annotation with a link back to the issue.
- 4It opens a merge request on a new branch with a descriptive title and body.
- 5It resolves the code owner from CODEOWNERS and assigns them as reviewer, then comments on the tracking issue with the MR link.
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.