From tac
Analyzes failed test JSON from /test, reproduces via execution command, fixes code root cause minimally, verifies with re-run and full suite.
How this skill is triggered — by the user, by Claude, or both
Slash command
/tac:resolve-failed-testThis skill is limited to the following tools:
The summary Claude sees in its skill listing — used to decide when to auto-load this skill
Analyze a failed test, fix the underlying issue, and verify the fix.
Analyze a failed test, fix the underlying issue, and verify the fix.
test_result: $ARGUMENTS - JSON object from /test command with failed test detailsExpects a JSON object from the /test command:
{
"test_name": "unit_tests",
"passed": false,
"execution_command": "pytest tests/test_auth.py -v",
"test_purpose": "Validates authentication functionality",
"error": "AssertionError: Expected status 200, got 401"
}
Review the test result:
Identify the root cause by understanding:
IMPORTANT: Use the exact execution_command from the test result:
# Run the exact command to confirm failure
{execution_command}
Verify you see the same error. This ensures you're fixing the right problem.
Apply a fix following these principles:
Re-run the exact same execution_command:
{execution_command}
Success criteria: Test now passes (exit code 0, no failures)
If the specific test passes, run the full test suite to check for regressions:
# Run complete test suite
[full test command]
Report your resolution:
## Resolution Complete
### Failure Analysis
- **Test**: {test_name}
- **Root Cause**: [What caused the failure]
- **Error**: {error}
### Fix Applied
- **File(s) Modified**: [list of files]
- **Change Summary**: [brief description]
### Validation
- **Specific Test**: PASS
- **Full Suite**: PASS/FAIL
- **Command Used**: {execution_command}
### Notes
[Any observations or recommendations]
If the fix doesn't work:
Maximum 3 retry attempts before escalating.
This command is the RESOLVE phase:
/test → [failure JSON] → /resolve-failed-test {result} → /test
↓
[verify fix]
npx claudepluginhub melodic-software/claude-code-plugins --plugin tacGuides systematic test failure investigation with dual hypotheses (test vs. code issue), step-by-step protocol, red flags, and best practices.
Guides systematic investigation of test failures using dual-hypothesis approach (test wrong vs. implementation bug) and step-by-step protocol. Use for diagnosing test errors or establishing test failure mindset.
Analyzes failing test cases to classify failures as test bugs, implementation bugs, or ambiguous. Uses investigative process to verify expectations against code and docs before recommending fixes.