ENGINEERING
Weekly flaky-test offender digest to Slack
Every Monday, ranks the top flaky specs by failure frequency over the past week from stored CI history and posts a digest to Slack with owners, flake rates, and direct links…
How it runs
The automated pipeline, trigger to output.
- TriggerSchedule: every Monday morning
- ActionAggregate 7-day flake stats from historyPostgres
- LogicFilter to noise floor and rank top offenders
- OutputPost ranked digest to Slack channelSlack
What it does
Gives the team a recurring, ranked view of which tests are wasting the most CI time. Instead of one-off complaints in chat, it produces a single authoritative weekly leaderboard of flaky offenders so the worst ones actually get fixed.
When to use it
Run this when you already capture per-run test results and want sustained pressure to burn down the quarantine list. Ideal for a weekly eng sync or a dedicated reliability channel.
How it works
- 1A scheduled trigger fires every Monday morning.
- 2The flow queries the CI history table in Postgres for the past seven days, aggregating flips, total failures, and CI minutes lost per spec.
- 3It joins each spec to its CODEOWNERS-derived owner and any open quarantine issue.
- 4A logic step keeps only specs above the noise floor and sorts them into a top-N leaderboard.
- 5A formatted Slack message is posted to the reliability channel with rank, flake rate, owner mention, and issue link, so the worst offenders are unmissable.
Set it up
What you configure once, before turning it on.
- 1Connect PostgresAny Postgres URL — query, write, migrate.
- 2Connect SlackChannels, DMs, threads, mentions.
- 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
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…
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.
Scan for deprecated endpoints and email consumers a weekly sunset countdown
On a weekly schedule, scans the OpenAPI spec for endpoints marked deprecated with a sunset date, and emails each consuming team a countdown of how many days remain before removal.
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.
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.
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.