ENGINEERING
Quarantine a Flaky Test on CI Failure and File the Owner
When a CI run reports an intermittent test failure, this workflow tags the test as quarantined, finds its code owner from CODEOWNERS.
How it runs
The automated pipeline, trigger to output.
- TriggerGitHub workflow_run completed webhookGitHub
- LogicDetect flaky signature (failed on retry after prior pass)
- ActionResolve owner from CODEOWNERS for failing fileGitHub
- ActionOpen quarantine PR adding skip annotationGitHub
- ActionCreate assigned Linear issue with 14-day due dateLinear
- OutputComment issue link back on the CI runGitHub
What it does
Catches tests that fail intermittently on GitHub Actions, moves them into a quarantine state so they stop blocking merges, and immediately creates an accountable owner record in Linear with a deadline to fix and re-enable.
When to use it
Run this when a green-then-red test is wedging your main branch and you want to keep shipping without silently deleting coverage. It turns 'just skip it' into a tracked, owned, time-boxed task.
How it works
- 1A GitHub workflow_run completion webhook fires when a CI job finishes.
- 2A logic step inspects the run: only proceed if a test failed on a retry that previously passed (the flaky signature).
- 3The workflow reads CODEOWNERS for the failing test file to resolve the responsible team or person.
- 4It commits a skip annotation to the test file on a quarantine branch and opens a PR.
- 5A Linear issue is created, assigned to the resolved owner, labeled 'flaky-quarantine', with a due date 14 days out.
- 6The issue link is posted back as a comment on the originating CI run for traceability.
Set it up
What you configure once, before turning it on.
- 1Connect GitHubRepos, issues, pull requests, actions.
- 2Connect LinearIssues, projects, cycles, triage.
- 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.