Skill

flaky-test-investigation

Use to diagnose tests that pass and fail intermittently without code changes.

npx claudepluginhub yeaight7/agent-powerups --plugin debugging-diagnostics

Popularity

Parent stars

Parent forks

Invocation

How this skill is triggered — by the user, by Claude, or both

Slash command

/debugging-diagnostics:flaky-test-investigation

User invocable

Model invocable

Inline context

Default effort

Context Preview

The summary Claude sees in its skill listing — used to decide when to auto-load this skill

Flaky tests erode trust in CI. Do not just re-run them and hope for the best.

SKILL.md

19 lines · ~293 tokens

Similar Skills

ui-ux-pro-max

90.2k

Provides UI/UX resources: 50+ styles, color palettes, font pairings, guidelines, charts for web/mobile across React, Next.js, Vue, Svelte, Tailwind, React Native, Flutter. Aids planning, building, reviewing interfaces.

ui-ux-pro-max

context7-mcp

55.5k

Fetches up-to-date documentation from Context7 for libraries and frameworks like React, Next.js, Prisma. Use for setup questions, API references, and code examples.

context7-plugin

gitnexus-exploring

38.9k

Explores codebases via GitNexus: discover repos, query execution flows, trace processes, inspect symbol callers/callees, and review architecture.

1 file

gitnexus

Stats

LanguageTypeScript

Parent stars5

Parent forks1

MaintenanceExcellent

Last CommitMay 6, 2026

Actions

View Source View Plugin View on GitHub View README

Help us improve

Share bugs, ideas, or general feedback.

Stats

Actions

Help us improve

Share bugs, ideas, or general feedback.

Flaky Test Investigation

Flaky tests erode trust in CI. Do not just re-run them and hope for the best.

Investigation Protocol

Isolate the Test: Run the specific failing test by itself. If it passes, the flake is likely an order dependency or state leakage from a previous test.

Stress Test: Run the test in a tight loop (e.g., for i in {1..100}; do npm test -- -t "My Test"; done).

Check for Common Vectors:

Time: Does the test rely on Date.now() or setTimeout? Mock the clock.
Async/Promises: Are we asserting before a background task finishes? Ensure proper await or waitFor usage.
Shared State: Are we reusing database records, global singletons, or mutated variables between runs? Ensure clean teardowns in afterEach.
Randomness: Does the test rely on random IDs or sorts? Force deterministic seeds or sort orders.

Prove the Fix: Do not just guess. The fix must be verified by running the stress test loop again and achieving a 100% pass rate.