test-flakiness
FeaturedDetect non-deterministic (flaky) tests by reading CI run logs or test result history. Aggregates pass rates per test, identifies intermittent failures, recommends quarantine or fix, and maintains a flaky test registry. Best run during Polish phase or after multiple CI runs.
Install
Quality Score: 97/100
Skill Content
Details
- Author
- Donchitos
- Repository
- Donchitos/Claude-Code-Game-Studios
- Created
- 9 months ago
- Last Updated
- 1 weeks ago
- Language
- Shell
- License
- MIT
Integrates with
Similar Skills
Semantically similar based on skill content — not just same category
testdoc-flaky
Finds flaky tests from the JUnit XML that CI already produces: collects several runs of the same suite, ranks tests that both passed and failed by flake rate, guesses the cause (timing, shared state, network, randomness, time zone or date, resource limits) from the failure text, and proposes the smallest fix for that cause, never a blanket retry. Use when the user says "this test is flaky", "tests fail randomly in CI", "find my flaky tests", "which tests fail intermittently", "it passes on rerun", or "rank flaky tests".
flaky-test-triage
Triage an intermittently failing test suite: parse recent continuous integration runs, rank tests by failure rate, separate real regressions from timing noise, and quarantine what is wasting the team's afternoon. Use when reruns pass and a red build has stopped meaning anything. NOT for authoring the tests themselves (use test-authoring for that).
flaky-triage
Handles a test that passes and fails on the same code — confirms the flakiness, finds which of the five causes it is, then fixes or quarantines it. Use it for an intermittent failure, or when CI goes green on a re-run without a change.