ENGINEERING
Weekly Flaky-Test Digest and Auto-Close Recovered
Weekly report that summarizes all quarantined flaky tests, auto-closes tracking issues for tests that have passed cleanly for two weeks.
How it runs
The automated pipeline, trigger to output.
- TriggerWeekly schedule
- ActionList open flaky-test issues and recent outcomesGitHub
- LogicBucket recovered, still-flaky, worsening
- ActionAuto-close issues for recovered testsGitHub
- OutputPost weekly digest to DiscordDiscord
What it does
Once a week this workflow compiles the state of the flaky-test quarantine: which tests are still flaky, which have recovered, and which are getting worse. Tests that have passed cleanly across all runs for two weeks get their GitHub tracking issues automatically closed with a recovery note, and the full digest is posted to Discord for visibility.
When to use it
Use this to keep the quarantine from becoming a graveyard. It reclaims stabilized tests, surfaces persistent offenders, and gives the team a regular pulse on test-suite health without manual bookkeeping.
How it works
- 1A weekly schedule triggers the run.
- 2The bot lists open GitHub issues labeled `flaky-test` and reads recent CI outcomes for each from the results store.
- 3A decision step buckets each test as recovered, still flaky, or worsening based on its two-week pass record.
- 4It closes the issues for recovered tests with a recovery comment and leaves the rest open.
- 5It posts a formatted weekly digest — counts per bucket and top offenders — to the team Discord channel.
Set it up
What you configure once, before turning it on.
- 1Connect GitHubRepos, issues, pull requests, actions.
- 2Connect DiscordCommunity channels + voice + bots.
- 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
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.