Flaky Test Detector

Detect, analyze, and fix flaky tests across any test runner. Use when tests intermittently fail in CI, tests pass locally but fail on CI, tests fail non-deterministically, or need to stabilize a flaky test suite. Also for 'flaky test', 'flaky', 'intermittent failure', 'unstable test', 'test flakiness', 'test retry', 'CI flaky', 'non-deterministic test'.

4 stars 2 forksTesting & QA

Install

skills CLI (Claude Code, Cursor, Codex and more)

npx skills add sametcelikbicak/flaky-test-detector --skill Flaky Test Detector

Manual install

git clone --depth 1 https://github.com/sametcelikbicak/flaky-test-detector.git /tmp/flaky-test-detector
mkdir -p ~/.claude/skills
cp -r /tmp/flaky-test-detector/. ~/.claude/skills/Flaky-Test-Detector

Personal skills live in ~/.claude/skills. Use .claude/skills in a project folder to share a skill with your team.

From the SKILL.md

# Flaky Test Detector

Identify, diagnose, and eliminate flaky tests. Runs your test suite multiple times, isolates non-deterministic failures, categorizes root causes, and applies targeted fixes.

## Pipeline

1. **Detect** runner & configuration
2. **Harvest** flaky candidates via repeated runs
3. **Analyze** failure patterns to identify root cause
4. **Fix** each flakiness category with proven strategies
5. **Verify** fixes by re-running the detection loop

---

## Phase 1: Detect runner and configuration

Read project setup:

```bash
cat package.json
```

Identify the test runner:

| Indicator | Runner | Base command |
|---|---|---|
| `"vitest"` in devDependencies | **Vitest** | `npx vitest` |
| `"jest"` in devDependencies | **Jest** | `npx jest` |
| `"react-scripts"` in devDependencies | **react-scripts** | `npx react-scripts test` |
| `"@playwright/test"` in devDependencies | **Playwright** | `npx playwright test` |
| `"cypress"` in devDependencies | **Cypress** | `npx cypress run` |
| `"mocha"` in devDependencies | **Mocha** | `npx mocha` |
| `"ava"` in devDependencies | **AVA** | `npx ava` |

Check existing retry/flaky config:

- **Vitest**: `retry` in `vitest.config.ts`
- **Jest**: `testRetry` in `jest.config.ts` or `jest.retryTimes()` in setup
- **Playwright**: `retries` in `playwright.config.ts`
- **Cypress**: `retries` in `cypress.config.ts`
- **Mocha**: `--retries` CLI flag or `retries` in `.mocharc.json`

Read the full skill on GitHub

Details

Skill name: Flaky Test Detector
Repository: sametcelikbicak/flaky-test-detector
License: MIT
Repo updated: 11 September 2026
Listed in: heilcheng/awesome-agent-skills

FAQ

What does the Flaky Test Detector skill do?

How do I install the Flaky Test Detector skill?

skills CLI (Claude Code, Cursor, Codex and more): npx skills add sametcelikbicak/flaky-test-detector --skill Flaky Test Detector. Skills go in ~/.claude/skills (personal) or .claude/skills (project), and Claude loads them automatically when a task matches the description.

Is Flaky Test Detector popular?

It lives in sametcelikbicak/flaky-test-detector, which has 4 GitHub stars and 2 forks, and is included in 1 curated skill list.

Related skills

Playwright Skill

appautomaton/playwright-skill

Complete browser automation with Playwright. Auto-detects dev servers, writes clean test scripts to $TMPDIR (or /tmp). Test pages, fill forms, take screenshots, check responsive design, validate UX, test login flows, check links, automate any browser task. Use when user wants to test websites, automate browser interactions, validate web functionality, or perform any browser-based testing.

Testing & QA

Playing to Win

paultaki/playing-to-win

This skill should be used when the user asks to evaluate, sharpen, red-team, or pressure-test a business idea, offer, market choice, product, or strategic move using Roger Martin and A.G. Lafley's Playing to Win choice cascade. Triggers on phrases including "Playing to Win", "P2W", "where to play", "how to win", "winning aspiration", "build me a strategy", "red-team this idea", "pressure-test this", "Plan to Win", or "build a strategy framework around this project". Produces a structured 12-section output across four phases (Diagnosis, Cascade, Stress Test, Verdict), writes a persistent markdo

Testing & QA

Serenity Interactive Chain

submato/serenity-interactive-chain-skill

Creates a Serenity-style interactive self-contained HTML mindmap for industries, companies, groups, and ecosystems: first split a company into business domains when needed, then produce a project-local `.html` file in the Musk Ecosystem Mindmap pattern with an expandable tree, selected-node detail, evidence grades, public/private companies, A股/港股 mappings, recent 3-month/6-month/1-year price performance for recommended research names, catalysts, falsification tests, copy-to-clipboard drilldown prompts, and bottom stock-detail cards. This skill must output HTML only, never `.canvas.tsx`. Use wh

Testing & QA

Autogrind

ttttonyhe/autogrind

Engage in 24x7 auto-work mode. Continuously grind through improvements, fixes, tests, and polish without stopping until you say so. For long-running sessions across code, ML/data, research, design, or writing. Not for single bounded tasks. Trigger phrases: /autogrind, /自己动, 'autogrind this', 'grind on this', 'keep working don't stop', 'work until I say stop', 'keep improving', 'keep going'.

Testing & QA

Senior QA Engineer

javalenciacai/QASkills

Behave as a Senior QA Engineer covering the complete software testing lifecycle from requirements analysis through test automation and continuous improvement. Always orchestrate available skills to determine the best approach before executing tasks.

Testing & QA

Supertest

renanmpimentel/supertest

Use when creating, changing, running, or auditing unit and integration tests, investigating tests that pass without observing outcomes, or analyzing application mutations and Necessist findings.

Testing & QA

Browse the most popular Claude skills, all testing & qa skills, or write your own with the skills generator.