ENGINEERING
Detect Flaky Tests on CI Re-run and Open a Deflake Ticket
When a GitHub Actions job that failed on the first attempt passes on a re-run for the same commit, flag the offending tests as flaky and open a tracked Linear deflake ticket.
How it runs
The automated pipeline, trigger to output.
- TriggerGitHub workflow_run completedGitHub
- LogicIs this a passing re-run of a previously failed SHA?
- ActionDiff job logs to extract red-to-green testsGitHub
- LogicDedupe against open deflake tickets
- ActionCreate or update Linear deflake ticketLinear
- OutputPost flake summary to SlackSlack
What it does
It catches the classic flaky-test signature: a CI job fails, someone hits "re-run," and the second attempt passes with no code change. The workflow compares the failed and passed runs for the same commit SHA, extracts the tests that flipped, and files a Linear ticket so the flake is tracked instead of silently re-run forever.
When to use it
Use it when your team's habit is to re-run red CI until it goes green. That habit hides intermittent failures and erodes trust in the suite. This turns every "it passed the second time" into a logged, ownable task.
How it works
- 1A GitHub `workflow_run` completed event fires when any CI run finishes.
- 2A logic step checks whether this is a re-run (attempt > 1) that succeeded while a prior attempt for the same SHA failed.
- 3If so, an action pulls both runs' job logs and diffs the failing test names to isolate which tests flipped red-to-green.
- 4A logic step dedupes against open deflake tickets so repeat flakes append rather than spawn duplicates.
- 5A Linear action creates or updates a ticket with the test names, run URLs, and commit.
- 6A Slack message posts the new flake to the team channel.
Set it up
What you configure once, before turning it on.
- 1Connect GitHubRepos, issues, pull requests, actions.
- 2Connect LinearIssues, projects, cycles, triage.
- 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.
