Skip to main content
Each recipe solves one problem end to end, with the calls, code and configuration it needs. Some run as a script or a CI step, some as a small service, and some hand the work to a coding agent such as Cursor or Claude Code.

Fix

Fix Flaky Tests

Give a coding agent the context it needs to fix a flaky test.

Autofix CI Failures

Have a coding agent investigate a red CI run and open a fix.

Tighten Test Timeouts

Bring inflated timeouts down to fit each test’s passing runtime.

Guard

Evaluate Release Branch Test Health

Report the failing tests on a release branch before you cut a release.

Never Quarantine Tests in Protected Paths

Keep every test under the paths you choose out of quarantine.

Notice

Explain a Failed Pull Request

Tell the author which failed tests are known flaky and which are probably real.

Route Flaky Tests to Their Owners

File a ticket for a newly flaky test’s owners and tell their team in Slack.

Alert When a Test Escalates

Send a Slack alert when a test gets worse, not only when it’s first flagged.

Post a Weekly Flaky Test Digest

Post the tests that changed status this week to Slack, grouped by owner.