ENGINEERING
Auto-Unquarantine Tests After a Clean Stability Streak
On a schedule, checks the ledger for quarantined tests that have passed cleanly across enough recent runs, removes them from quarantine.
How it runs
The automated pipeline, trigger to output.
- TriggerDaily schedule fires
- ActionQuery quarantined tests and recent run historyBigQuery
- LogicSelect tests with clean pass streak over threshold
- ActionClear quarantine flag in the ledgerBigQuery
- ActionOpen PR removing the quarantine skipGitHub
- OutputClose the deflake issue with a resolution noteLinear
What it does
Quarantine should be temporary. This workflow finds tests that have been quarantined but have since passed cleanly across a configurable number of consecutive runs, marks them stable in the ledger, opens a pull request that re-enables them in the test config, and closes the tracking deflake issue. It prevents the quarantine list from silently growing forever.
When to use it
Use it to reclaim test coverage automatically after fixes land, and to keep your quarantine list honest so it reflects only genuinely unstable tests rather than ones already healed.
How it works
- 1A daily schedule trigger fires.
- 2The flow queries the BigQuery ledger for quarantined tests and their recent run history.
- 3Logic selects tests with an unbroken clean pass streak above the threshold.
- 4The ledger marks those tests as stable and clears the quarantine flag.
- 5A GitHub pull request is opened removing the quarantine skip from the test config.
- 6Each corresponding Linear deflake issue is closed with a resolution note.
Set it up
What you configure once, before turning it on.
- 1Connect BigQueryDatasets, queries, schemas.
- 2Connect GitHubRepos, issues, pull requests, actions.
- 3Connect LinearIssues, projects, cycles, triage.
- 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
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.