ENGINEERING
Mainline flaky-storm detector: page on-call when the same test flakes repeatedly
Watches main-branch CI failures and, when one test flakes more than N times in a rolling window, pages the on-call engineer via PagerDuty and files a high-priority Linear ticket…
How it runs
The automated pipeline, trigger to output.
- TriggerMain-branch CI failureGitHub
- LogicCount flakes of this test in rolling window
- LogicCompare to storm threshold
- ActionTrigger PagerDuty incident for on-callPagerDuty
- OutputFile high-priority linked Linear ticketLinear
What it does
Distinguishes a single annoying flake from a flaky storm that's blocking everyone's merges on the main branch. It counts repeated flaky failures of the same test in a short window, and when one crosses the storm threshold it treats the situation as an incident.
When to use it
Use when a flaky test on main can grind the whole team's deploys to a halt. Routine flakes get a normal ticket elsewhere; this workflow is the loud path that wakes someone up only when a test is actively causing a pile-up.
How it works
- 1A GitHub webhook fires on each main-branch CI failure.
- 2The flow records the failure and counts how many times that test flaked in the rolling window.
- 3A branch checks the count against the storm threshold (e.g. 3 flakes in 2 hours).
- 4Below threshold, it logs and exits quietly.
- 5At or above threshold, it triggers a PagerDuty incident for the on-call engineer.
- 6It files a high-priority Linear ticket with the storm timeline and links it to the incident.
Set it up
What you configure once, before turning it on.
- 1Connect GitHubRepos, issues, pull requests, actions.
- 2Connect PagerDutyIncidents, on-call, escalations.
- 3Connect LinearIssues, projects, cycles, triage.
- 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.