ENGINEERING
MR Pipeline Retry Guard with Flaky Lookup
On every merge-request pipeline failure, looks up whether the failing specs are known-flaky and posts a comment telling the author exactly which failures are safe to retry versus…
How it runs
The automated pipeline, trigger to output.
- TriggerGitLab MR pipeline failed webhookGitLab
- ActionParse failed specs from JUnit reportGitLab
- ActionLook up specs in flaky-test registryPostgres
- LogicPartition known-flaky vs likely-real failures
- OutputPost verdict comment and tag safe-to-retry on MRGitLab
What it does
Stops developers from guessing on red MR pipelines. When an MR pipeline fails, it parses the failing tests and checks each against the known-flaky registry, then posts a single MR comment that separates "known-flaky, safe to retry" failures from "not flaky, needs a fix" failures so the author knows whether a retry is justified.
When to use it
Use it when contributors waste cycles re-running pipelines hoping flakiness clears, or worse, retry away a genuine failure. This gives an authoritative per-failure verdict right in the MR.
How it works
- 1A GitLab merge-request pipeline-failed webhook fires.
- 2The flow fetches the JUnit report and extracts each failed spec.
- 3A Postgres lookup matches each failure against the flaky-test registry maintained by the quarantine bot.
- 4A logic step partitions failures into known-flaky versus likely-real.
- 5It writes a structured GitLab MR note: flaky failures with a retry suggestion, real failures called out as blocking.
- 6If every failure is known-flaky, it adds a `safe-to-retry` label to the MR.
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.