ENGINEERING
Re-enable stabilized tests and page on quarantine release-blocks
Daily, checks quarantined tests against recent CI history: opens a PR to un-quarantine any test that has been green for a sustained window.
How it runs
The automated pipeline, trigger to output.
- TriggerDaily schedule fires
- ActionRead quarantined tests and recent results from GitHubGitHub
- LogicSplit into stable-to-re-enable vs still-flaky
- ActionOpen PR removing quarantine for stable testsGitHub
- ActionPage on-call for release-critical still-quarantined testsPagerDuty
- OutputPost re-enable and escalation summary to SlackSlack
What it does
Closes the loop on quarantine so tests do not stay disabled forever. It reviews the set of currently quarantined tests, measures their recent stability from CI run history, and re-enables the ones that have proven reliable again. It also catches the dangerous case where a quarantined test guards a release-critical path and escalates it.
When to use it
Use it once you have an automated or manual quarantine process and need to prevent permanent coverage gaps. Essential for teams with release gates that quarantine could silently weaken.
How it works
- 1A daily schedule fires the workflow.
- 2It reads the quarantined-test list and their recent results from GitHub run history.
- 3A logic step splits tests into 'stable enough to re-enable' versus 'still flaky' using a sustained-green window.
- 4For stable tests it opens a GitHub PR removing the quarantine annotation.
- 5For still-quarantined tests on a release-critical path it pages on-call via PagerDuty.
- 6It posts the day's re-enable and escalation summary to Slack.
Set it up
What you configure once, before turning it on.
- 1Connect GitHubRepos, issues, pull requests, actions.
- 2Connect PagerDutyIncidents, on-call, escalations.
- 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
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.