ENGINEERING
Escalate Repeat-Offender Flaky Tests to PagerDuty
When a flaky test is filed for the third time in a rolling 30-day window, escalates it as a PagerDuty incident to the owning team and bumps the Linear issue priority to urgent.
How it runs
The automated pipeline, trigger to output.
- TriggerWebhook: flaky-test issue created or reopenedHTTP webhook
- ActionCount prior filings for the test in last 30 daysLinear
- LogicProceed only on third strike within window
- ActionSet Linear issue to urgent and assign team leadLinear
- OutputTrigger PagerDuty incident with flake historyPagerDuty
What it does
Applies pressure to the worst chronic flakes. A test that keeps getting re-quarantined despite prior fixes is a reliability liability. This counts repeat filings per test and, on the third strike within 30 days, pages the owning team and escalates the tracking issue to urgent — making the flake impossible to keep deferring.
When to use it
Use it when a handful of tests flake repeatedly, get patched superficially, and return. It enforces accountability by turning chronic flakiness into a paged incident.
How it works
- 1A webhook fires each time a flaky-test issue is created or reopened.
- 2An action counts prior quarantine filings for the same test in the last 30 days from the issue store.
- 3A logic step proceeds only when the count reaches the third strike.
- 4An action sets the Linear issue priority to urgent and assigns the owning team lead.
- 5An output triggers a PagerDuty incident routed to the team's service with the flake history and links.
Set it up
What you configure once, before turning it on.
- 1Connect HTTP webhookTrigger any URL on agent actions.
- 2Connect LinearIssues, projects, cycles, triage.
- 3Connect PagerDutyIncidents, on-call, escalations.
- 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.