ENGINEERING
Nightly re-test and rehabilitate quarantined specs
Each night, re-runs every quarantined spec multiple times in isolation; specs that pass a configured number of consecutive runs get their quarantine removed, a cleanup PR opened.
How it runs
The automated pipeline, trigger to output.
- TriggerSchedule: nightly re-test run
- ActionDispatch isolated re-runs of quarantined specsGitHub
- ActionRecord consecutive-pass streaksPostgres
- LogicSelect specs meeting clean-streak threshold
- OutputOpen cleanup PR and close quarantine issueGitHub
What it does
Prevents the quarantine list from becoming a graveyard. It actively verifies whether quarantined specs have stabilized — either because the underlying flake was fixed or the environment changed — and automatically promotes proven-stable specs back into the active suite.
When to use it
Use this alongside any quarantine program so isolated tests are continuously re-evaluated instead of forgotten. It is the rehabilitation half of the workflow.
How it works
- 1A nightly schedule trigger fires.
- 2The flow reads the current quarantine list from Postgres and dispatches an isolated re-run of each spec via the GitHub Actions API, repeated several times.
- 3It records the streak of consecutive passes per spec back to the history table.
- 4A logic branch selects specs that hit the required clean-streak threshold.
- 5For each promoted spec it opens a cleanup PR removing the skip annotation and closes the associated quarantine issue with the passing evidence.
Set it up
What you configure once, before turning it on.
- 1Connect GitHubRepos, issues, pull requests, actions.
- 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
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.