ENGINEERING
Auto-Skip Flaky Test via Quarantine MR
On a confirmed flaky test, opens a GitLab merge request that adds a skip annotation referencing a tracking issue, so the test stops blocking the pipeline immediately.
How it runs
The automated pipeline, trigger to output.
- TriggerIssue labeled auto-skip (GitLab webhook)GitLab
- ActionRead issue for test path and idGitLab
- LogicSkip if test already quarantined
- ActionCommit skip annotation to a new branchGitLab
- ActionOpen quarantine merge requestGitLab
- OutputComment MR link on tracking issueGitLab
What it does
This workflow doesn't just file paperwork — it removes the flaky test from the critical path. When a flaky test is confirmed, it opens a GitLab merge request that adds a skip/quarantine annotation to the test, linked back to a tracking issue, so the next pipeline run is green while the root cause stays visible.
When to use it
Reach for this when a single flaky test is repeatedly blocking merges and you want it auto-skipped within minutes, not after a manual triage cycle. The MR keeps a human in the loop to approve the skip.
How it works
- 1A GitLab webhook fires when a quarantine tracking issue is labeled `auto-skip`.
- 2The flow reads the issue to extract the test path and identifier.
- 3A logic step confirms the test isn't already skipped to avoid duplicate MRs.
- 4It creates a branch and commits a skip annotation (e.g. `@pytest.mark.skip` / `it.skip`) referencing the issue number.
- 5It opens a merge request with the change, requesting review from the test's last author.
- 6It comments on the original issue linking the quarantine MR.
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.