ENGINEERING
Flaky test detector: quarantine reruns and file owner-assigned Linear tickets
On every GitHub Actions CI failure, reruns the failed tests in isolation to confirm flakiness.
How it runs
The automated pipeline, trigger to output.
- TriggerGitHub Actions CI run failsGitHub
- ActionRerun failed tests in isolationGitHub
- LogicPass on retry = flaky, else real failure
- ActionCommit quarantine skip annotation as a PRGitHub
- ActionResolve test file CODEOWNERGitHub
- OutputFile owner-assigned Linear ticketLinear
What it does
Catches tests that fail intermittently rather than for a real regression. When CI goes red, it isolates the failing tests, reruns them, and if they pass on retry it marks them flaky, adds a skip annotation, and opens a Linear ticket routed to whoever owns that file.
When to use it
Use when flaky tests are blocking merges and developers are blindly re-running pipelines. It stops the rerun roulette by quarantining the offender and assigning a real owner, so the main branch stays green without hiding the debt.
How it works
- 1A GitHub Actions workflow_run failure fires the webhook with the failed job and test names.
- 2The flow reruns just the failed tests in isolation via a GitHub dispatch.
- 3A branch checks the rerun result: pass-on-retry means flaky; fail again means a real break and the flow exits.
- 4For flaky tests, it commits a quarantine annotation (skip + tag) on a new branch and opens a PR.
- 5It resolves the test file's CODEOWNER from GitHub.
- 6It files a Linear ticket assigned to that owner with logs, rerun history, and the quarantine PR link.
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.