ENGINEERING
Weekly Flaky-Test Health Digest from the Ledger
On a weekly schedule, queries the BigQuery flake ledger for top offenders, week-over-week trend, and quarantine churn, then publishes a Confluence page and a Slack summary.
How it runs
The automated pipeline, trigger to output.
- TriggerWeekly schedule fires
- ActionQuery trailing-week metrics from flake ledgerBigQuery
- LogicRank offenders and compute week-over-week trend
- ActionPublish or update Confluence health pageConfluence
- OutputPost top-offender summary to SlackSlack
What it does
Once a week it turns the raw flake ledger into a readable health report: the worst offenders by flake rate, how the overall flake count moved versus last week, which tests newly entered or exited quarantine, and total CI rerun time burned by flakes. It publishes a Confluence page for the record and a short Slack post for visibility.
When to use it
Use it to give engineering leadership and the test-infra team a recurring, no-effort pulse on test suite health and to keep deflaking work prioritized against the tests that hurt most.
How it works
- 1A weekly schedule trigger fires (e.g. Monday morning).
- 2The flow runs aggregate queries against the BigQuery flake ledger for the trailing week.
- 3Logic ranks top offenders, computes week-over-week delta, and lists quarantine entries and exits.
- 4It renders the metrics into a structured report body.
- 5A Confluence page is created or updated under the team's space.
- 6A concise summary with the top three offenders and the trend is posted to Slack.
Set it up
What you configure once, before turning it on.
- 1Connect BigQueryDatasets, queries, schemas.
- 2Connect ConfluenceSpaces, pages, blueprints.
- 3Connect SlackChannels, DMs, threads, mentions.
- 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
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.