ENGINEERING
Auto-quarantine tests that fail then pass on rerun
When a GitHub Actions job fails and a retry of the same commit passes, it identifies the offending test, opens a PR that adds a skip/quarantine annotation.
How it runs
The automated pipeline, trigger to output.
- TriggerGitHub workflow_run completed eventGitHub
- LogicDetect fail-then-pass retry on the same commit
- ActionOpen PR adding the quarantine annotationGitHub
- ActionFile Linear issue to track the fixLinear
- OutputNotify code owner in Slack with the PRSlack
What it does
Turns the classic 'failed, hit retry, went green' signal into automatic quarantine. It compares the failing and passing attempts of the same workflow run, isolates the test that flipped, and proposes a code change that marks it as quarantined so it stops blocking unrelated PRs while a fix is pending.
When to use it
Use it on busy trunk-based repos where a single intermittent test can stall every merge. Best when your test framework supports a skip or quarantine annotation and you want a human to still approve the PR.
How it works
- 1A GitHub workflow_run completion event triggers the flow.
- 2A logic step checks whether an earlier attempt failed while a later attempt of the same SHA passed; non-matching events stop here.
- 3It diffs the attempt results to pin down the exact test that flipped.
- 4It opens a GitHub PR adding the quarantine annotation and a link back to the evidence.
- 5It files a Linear issue to track the underlying fix and links the PR.
- 6It pings the code owner in Slack with the quarantine PR for review.
Set it up
What you configure once, before turning it on.
- 1Connect GitHubRepos, issues, pull requests, actions.
- 2Connect LinearIssues, projects, cycles, triage.
- 3Connect SlackChannels, DMs, threads, mentions.
- 4Set each agent's modelWe leave models unset so you pick the tier — fast + cheap, or top-quality.
- 5Tune it to your dataEdit the prompts, filters, and field mappings so it matches how your team works.
- 6Test, 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.