ENGINEERING
Flaky-Test Recovery and Auto-Unquarantine
Periodically re-runs quarantined specs in isolation; when a test passes consistently across several runs it reverses the quarantine, closes the tracking issue.
How it runs
The automated pipeline, trigger to output.
- TriggerSchedule every few days
- ActionList open quarantine issues and their specsGitLab
- ActionRe-run each spec in isolation N timesGitLab
- LogicRequire clean sweep across all runs
- ActionOpen un-quarantine MR and close issueGitLab
- OutputNotify original reporter in SlackSlack
What it does
Keeps quarantine from becoming a graveyard. On a schedule it re-executes each quarantined spec several times in isolation, and when a test passes cleanly across all attempts it removes the skip annotation, closes the GitLab tracking issue, and tells the person who filed it that the test is healthy again.
When to use it
Use it when quarantined tests accumulate and lose coverage value because nobody revisits them. This proves stability before reinstating a test and gives credit back to the original reporter.
How it works
- 1A schedule trigger fires every few days.
- 2The flow lists open `flaky::quarantine` issues and the specs they reference.
- 3A GitLab pipeline triggers each spec in isolation, repeated N times (default 10).
- 4A logic step checks for a clean sweep across all runs.
- 5For consistent passers it opens an MR removing the quarantine annotation and closes the tracking issue.
- 6A Slack DM notifies the original reporter that their test was unquarantined.
Set it up
What you configure once, before turning it on.
- 1Connect GitLabRepos, MRs, pipelines, registry.
- 2Connect SlackChannels, DMs, threads, mentions.
- 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
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.