Stats
Actions
Tags
Runs full test suite, analyzes failures to identify root causes and patterns, categorizes into groups, and suggests prioritized fixes.
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>
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.
/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.
/diagnose-flakyDiagnoses flaky tests via decision tree, identifying root causes like interdependence, timing, environment differences before fixes. Uses pytest, grep, bash diagnostics.
/analyze-testsAnalyzes Python test suites in current or specified directories for quality, coverage, structure, patterns, and performance, reporting metrics, scores, and improvement recommendations.