ENGINEERING
Weekly flake-rate scorecard from Datadog CI Visibility
Pulls per-test flakiness metrics from Datadog CI Visibility each week, ranks the worst offenders by flake rate and merge-blocking impact.
How it runs
The automated pipeline, trigger to output.
- TriggerWeekly schedule fires
- ActionQuery Datadog CI Visibility flake metricsDatadog
- LogicRank offenders and compute week-over-week trend
- ActionOpen Linear issue for tests over critical thresholdLinear
- OutputPost weekly scorecard to SlackSlack
What it does
Gives engineering leadership a regular, data-backed view of which tests are wasting the most CI time. It queries Datadog CI Visibility for flaky-test and rerun metrics, ranks tests by flake rate and the number of pipelines they blocked, and turns it into a digestible weekly scorecard.
When to use it
Use it when CI test results already flow into Datadog and you want a recurring leadership-facing summary rather than per-incident alerts. Ideal for sprint reviews and reliability standups.
How it works
- 1A weekly schedule fires the workflow.
- 2It queries Datadog CI Visibility for flaky-test and rerun metrics over the trailing seven days.
- 3A logic step ranks tests by flake rate and blocked-pipeline count, and computes the change versus the prior week.
- 4It optionally opens a Linear issue for any test crossing a critical flake threshold.
- 5It posts a formatted scorecard with the top offenders and trend arrows to the team Slack channel.
Set it up
What you configure once, before turning it on.
- 1Connect DatadogMetrics, traces, log search.
- 2Connect LinearIssues, projects, cycles, triage.
- 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
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.