install
source · Clone the upstream repo
git clone https://github.com/genesiscz/GenesisTools
Claude Code · Install into ~/.claude/skills/
T=$(mktemp -d) && git clone --depth=1 https://github.com/genesiscz/GenesisTools "$T" && mkdir -p ~/.claude/skills && cp -r "$T/.claude/old/skills/analyze-test-failures" ~/.claude/skills/genesiscz-genesistools-analyze-test-failures && rm -rf "$T"
manifest:
.claude/old/skills/analyze-test-failures/SKILL.mdsource content
Analyze Test Failures
Run tests and diagnose failures in an isolated sub-agent context. This prevents heavy test output from cluttering your main session.
Usage
/analyze-test-failures [--file=path] [--filter=testname]
Examples
# Analyze all failing tests /analyze-test-failures # Analyze specific test file /analyze-test-failures --file=tests/Services/ReservationServiceTest.php # Analyze specific test method /analyze-test-failures --filter=testReservationCreation
What This Does
- Runs tests in a forked context (isolated execution)
- Parses failures without polluting main session
- Generates report with root causes and fixes
- Returns to main session with clean summary
Why Fork Context?
- Test output can be massive (phpunit verbose output)
- Analysis happens independently without affecting your main conversation
- Main session stays clean and focused
- Easy to retry or run with different filters