Stats
Actions
Tags
'%20stop-opacity%3D'0.16'%2F%3E%3Cstop%20offset%3D'1'%20stop-color%3D'rgb(200%2C90%2C60)'%20stop-opacity%3D'0.03'%2F%3E%3C%2FlinearGradient%3E%3C%2Fdefs%3E%3Crect%20width%3D'320'%20height%3D'200'%20fill%3D'url(%23g)'%2F%3E%3Ccircle%20cx%3D'250'%20cy%3D'56'%20r%3D'92'%20fill%3D'rgb(200%2C90%2C60)'%20fill-opacity%3D'0.06'%2F%3E%3Ccircle%20cx%3D'64'%20cy%3D'172'%20r%3D'58'%20fill%3D'rgb(200%2C90%2C60)'%20fill-opacity%3D'0.05'%2F%3E%3C%2Fsvg%3E)
Runs the test suite and analyzes failures to identify root causes, patterns, and suggest targeted fixes ranked by impact.
How this command is triggered — by the user, by Claude, or both
Slash command
/test-results-analyzer:analyze-failuresThe summary Claude sees in its command listing — used to decide when to auto-load this command
Analyze test failures to identify root causes, patterns, and suggest targeted fixes. ## Steps 1. Run the test suite and capture output: 2. Parse failing tests: 3. Categorize each failure: 4. Identify patterns across failures: 5. For each failure, trace to the root cause: 6. Suggest specific fixes ranked by impact: ## Format ## Rules - Always run the full test suite, not just failing tests. - Group related failures to avoid fixing the same issue multiple times. - Prioritize fixes that unblock the most tests.
Analyze test failures to identify root causes, patterns, and suggest targeted fixes.
Test Results: <passed>/<total> passed, <failed> failed
Failure Groups:
<category>: <count> tests
- <test name>: <root cause>
2plugins reuse this command
First indexed Mar 30, 2026
npx claudepluginhub rohitg00/awesome-claude-code-toolkit --plugin test-results-analyzer/test-fixDiagnoses failing tests, parses output, categorizes causes, reads code, applies targeted fixes, verifies with re-runs, and reports table of results with pass count.
/fix-failing-testDiagnose and fix a failing test by classifying its failure type, tracing the root cause, applying the minimal patch, and confirming no regressions.
/run-testsRuns a focused subset of the user's test suite via the mk-qa-master runner, surfaces failures with stack traces, and offers actionable next steps.
/debugAnalyzes Testany test execution failures using execution ID or problem description, retrieves logs, identifies root causes, and suggests fixes.
/diagnose-flakyDiagnoses flaky tests via decision tree, identifying root causes like interdependence, timing, environment differences before fixes. Uses pytest, grep, bash diagnostics.