ENGINEERING
Weekly Flaky-Test Quarantine Digest with Auto-Filed Cleanup Tasks
Aggregates the week's flaky-test signals, posts a ranked digest to Slack, and files a ClickUp cleanup task for each newly quarantined test.
How it runs
The automated pipeline, trigger to output.
- TriggerWeekly scheduled digest run
- ActionQuery flaky occurrences from metrics storePostgres
- LogicRank tests and split new vs existing quarantine
- ActionPost ranked flakiness digest to SlackSlack
- OutputFile ClickUp tasks for newly quarantined testsClickUp
What it does
This workflow gives engineering a single weekly view of CI instability. It rolls up all flaky-test signals recorded over the past week from your metrics store, ranks tests by flake frequency, posts a digest to Slack, and files a ClickUp cleanup task for every test that newly entered quarantine that week.
When to use it
Use it when per-run alerts are too noisy and you want one calm, recurring report that surfaces the top offenders and turns the new ones into tracked work. Ideal for a weekly engineering health review or sprint planning input.
How it works
- 1A scheduled trigger runs once a week.
- 2The flow queries the Postgres metrics store for flaky occurrences in the trailing seven days and ranks tests by frequency and affected pipelines.
- 3A branch separates tests already in quarantine from those newly crossing the threshold this week.
- 4It posts a ranked Slack digest with totals, top offenders, and trend versus the prior week.
- 5For each newly quarantined test it files a ClickUp cleanup task so nothing new slips through untracked.
Set it up
What you configure once, before turning it on.
- 1Connect PostgresAny Postgres URL — query, write, migrate.
- 2Connect SlackChannels, DMs, threads, mentions.
- 3Connect ClickUpDocs + tasks + chats in one workspace.
- 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.