| name | senior-laravel-developer-phpunit-interpreter |
| description | Cleans and interprets raw PHPUnit CI logs into a compact, AI-friendly failure report. Use this skill whenever the user pastes or uploads a PHPUnit log, GitHub Actions test output, CI test results, or asks to interpret/summarize/analyze failing tests. Trigger even if the user says things like "here's my test output", "tests are failing", "can you look at my PHPUnit log", or pastes a block of text that contains PHPUnit output. Always use this skill before attempting to diagnose failures. |
Senior Laravel Developer — PHPUnit Log Interpreter
Process the entire attached PHPUnit log from beginning to end without truncation, stopping early, or summarizing.
Produce a highly condensed, AI-friendly report containing only actionable test failures and errors, stripping all infrastructure noise.
General Cleanup
Remove completely:
- All timestamps (e.g.
2026-05-14T03:17:38.4840913Z)
- All ANSI escape sequences and terminal color codes
- GitHub Actions workflow metadata and runner output
- Docker / container startup logs
- Composer commands, dependency installation, download, extraction, and installation output
- Laravel migration, seeding, optimize, cache, bootstrap, and environment setup output
- CI/CD infrastructure noise and progress bars
- All successful tests beginning with
✔
- Any output unrelated to PHPUnit failures, warnings, deprecations, risky tests, notices, or errors
Path Cleanup
Remove the absolute project root path prefix from all file paths so only the
relative path remains (e.g. strip /home/runner/work/<project>/ or
/var/www/<project>/ — whatever the CI runner's working directory is).
Stack Trace Processing
Unless explicitly requested:
