From loopkit
Diagnoses flaky tests by running them in a loop and identifying common causes (timing/ordering, async races, resource leaks). Use when CI fails intermittently.
How this skill is triggered — by the user, by Claude, or both
Slash command
/loopkit:flaky-hunterWhen to use
intermittent CI failure, "passes locally fails in CI", a flaky test
The summary Claude sees in its skill listing — used to decide when to auto-load this skill
Run the suspect test 20x in a loop first — confirm it's actually flaky, not just broken.
Run the suspect test 20x in a loop first — confirm it's actually flaky, not just broken. Common causes, in order of likelihood:
retry(3) on a flaky test hides a real race that will bite in production. Quarantine only as a last resort, with a ticket.npx claudepluginhub archive228/loopkit --plugin loopkitDiagnoses non-deterministic test failures and eliminates root causes (timing, shared state, concurrency, external dependency, randomness) instead of retrying or skipping.
Diagnoses and eliminates flaky or nondeterministic tests by classifying failure types (ordering, timing, resource, environment, external, concurrency) and isolating root causes with reproducible fixes.
Reliability for your test suite. Runs tests repeatedly to detect flakiness, maintains a flaky registry, helps quarantine offenders to unblock CI, and guides root-cause analysis (timing, ordering, shared state).