Flaky Test Triage

Name: Flaky Test Triage
Availability: InStock
Rating: 4 (1 reviews)
Author: elorm

Run failing tests repeatedly, classify each failure as flaky or real, and fix only confirmed regressions.

High Quality

New

Join 0+ developers using this skill

Source:Loops! by elorm· free-to-copy

This loop is republished with attribution. Full credit and the original content belong to the source linked above.

command

Loops & Automation

intermediate

0 installs

4/5 quality

View Source

Last updated: June 19, 2026

AI Skill Market Insights

Real data. Real impact.

Popularity

Rising

Emerging

Active Users

Developers

Kickoff Prompt

Copy this prompt and run it with your agent to start the loop.

Start the "Flaky Test Triage" loop.

Goal: classify failing tests as flaky vs real and fix only real regressions
Max iterations: 5
Between iterations run: npm test -- --testPathPattern=<failing-suite>
Exit when: every failure is classified and real regressions are fixed or explicitly deferred

Step 1: Run the failing suite multiple times. Classify each failure, fix real ones, and document flaky behavior.

Self-pace this loop. After each iteration, run the check command, read the output, and only continue if the exit condition is not met. Stop when the exit condition passes or max iterations is reached. Give a short status update each pass.

TEAR & SHARE

2-3hrs/WK

RISING

0.0K+ USING

Kickoff prompt

Start the "Flaky Test Triage" loop.

Goal: classify failing tests as flaky vs real and fix only real regressions
Max iterations: 5
Between iterations run: npm test -- --testPathPattern=<failing-suite>
Exit when: every failure is classified and real regressions are fixed or explicitly deferred

Step 1: Run the failing suite multiple times. Classify each failure, fix real ones, and document flaky behavior.

Self-pace this loop. After each iteration, run the check command, read the output, and only continue if the exit condition is not met. Stop when the exit condition passes or max iterations is reached. Give a short status update each pass.

Steps

Run failing tests — Run the failing test file or suite 3–5 times. Record pass/fail pattern per test. (
```
npm test -- --testPathPattern=<failing-suite>
```
)
Classify failures — Label each failure as flaky (intermittent) or real (consistent). Note timing, ordering, or env dependencies.
Fix real failures — Fix confirmed real failures with minimal changes. For flaky tests, propose stabilization (retries, isolation, mocks).
Confirm stability — Re-run the suite multiple times to confirm real failures are gone and flakiness is reduced or documented. (
```
npm test -- --testPathPattern=<failing-suite>
```
)

Flaky Test Triage

AI Skill Market Insights

Kickoff Prompt

TEAR & SHARE

Tags

Architecture Documentation Builder

Be Part of the 0+ Developer Community

Kickoff prompt

Steps

License

Feature Scope Validator

Roadmap Builder

Performance Budget Guardian

Technical Debt Reduction

Channels

Learn

Compare

Company