ENGINEERING
Auto-Route Quarantined Flaky Tests to Owning Team in Linear
For each newly quarantined flaky test, finds the owning team from CODEOWNERS and opens a deflake issue in the right Linear team with failure evidence and a priority set…
How it runs
The automated pipeline, trigger to output.
- TriggerGitHub issue labeled 'quarantine'GitHub
- ActionResolve owning team from CODEOWNERS for test pathGitHub
- LogicDerive issue priority from flake rate and branch
- ActionCreate routed deflake issue in owning Linear teamLinear
- OutputBack-link Linear ticket onto the GitHub issueGitHub
What it does
When a test enters quarantine, it shouldn't sit in a spreadsheet — it needs an owner and a ticket. This workflow resolves the responsible team from the repo's CODEOWNERS for the test file path, then creates a Linear deflake issue on that team's board, pre-filled with recent failing runs, stack traces, and a priority derived from the flake rate.
When to use it
Use it once you have a quarantine signal (from your ledger workflow or a manual label) and you want every flaky test to land as actionable, correctly-routed work instead of getting lost.
How it works
- 1A GitHub issue labeled `quarantine` triggers the flow.
- 2The flow reads CODEOWNERS and maps the test's file path to the owning team.
- 3Logic computes priority: higher flake rate or main-branch impact bumps urgency.
- 4It assembles failure evidence — last failing run URLs and trimmed stack traces.
- 5A Linear issue is created on the owning team with the evidence, priority, and a `flaky` label.
- 6The originating GitHub issue is updated with a back-link to the Linear ticket.
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
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.