ENGINEERING
Flaky Test Triage to Owning Team in Linear
When a test is quarantined, this agent maps the failing test file to its owning team using CODEOWNERS and files a Linear issue on that team's board with full failure context…
How it runs
The automated pipeline, trigger to output.
- TriggerGitHub 'test-quarantined' label addedGitHub
- ActionResolve owning team from CODEOWNERSGitHub
- LogicSummarize failure evidence into issue body
- ActionCreate routed Linear issue with due dateLinear
- OutputComment Linear link back on PRGitHub
What it does
Quarantining a flaky test hides the symptom; this workflow assigns the cure. It reads the quarantined test path, resolves the responsible team from CODEOWNERS, and creates a Linear issue routed to that team with the failure history, affected branches, and a due date so flakes do not rot in quarantine forever.
When to use it
Use this when you have a quarantine process but no accountability — tests get skipped and never fixed. It closes the loop by putting a tracked, owned ticket in front of the team that wrote the code.
How it works
- 1A GitHub label event (test-quarantined) on a PR or issue triggers the flow.
- 2An action reads the CODEOWNERS file and matches the test path to a team.
- 3An agent summarizes the failure evidence into a clear issue body with reproduction notes.
- 4An action creates a Linear issue on the matched team with a deflake-by label and due date.
- 5The output posts the Linear issue link back as a comment on the originating PR.
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.