laravel:quality-checks
Quality Checks (Laravel)
Run automated checks before handoff or completion. Keep output clean.
PHP Style & Lint
# Check
sail pint --test # or: vendor/bin/pint --test
# Fix
sail pint # or: vendor/bin/pint
Static Analysis (choose your tool)
# PHPStan example
sail vendor/bin/phpstan analyse --memory-limit=1G # or: vendor/bin/phpstan analyse --memory-limit=1G
# Psalm example
sail vendor/bin/psalm # or: vendor/bin/psalm
Insights (optional, if installed)
sail artisan insights --no-interaction --format=json --flush-cache # or: php artisan insights --no-interaction --format=json --flush-cache
Tests
sail artisan test --parallel # or: php artisan test --parallel
Frontend (if applicable)
sail pnpm run lint # or: pnpm run lint
sail pnpm run types # or: pnpm run types
Checklist
- Pint clean (no errors)
- Static analysis passes
- Tests pass locally (parallel where possible)
- Frontend lint/types clean (if present)
- No noisy logs/errors during runs
More from jpcaparas/superpowers-laravel
laravel:routes-best-practices
Keep routes clean and focused on mapping requests to controllers; avoid business logic, validation, or database operations in route files
89laravel:blade-components-and-layouts
Compose UIs with Blade components, slots, and layouts; keep templates pure and testable
89laravel:performance-caching
Use framework caches and value/query caching to reduce work; add tags, locks, and explicit invalidation strategies for correctness
77laravel:eloquent-relationships
Define clear relationships and load data efficiently; prevent N+1, use constraints, counts/sums, and pivot syncing safely
76laravel:queues-and-horizon
Operate and verify queues with or without Horizon; safe worker flags, failure handling, and test strategies
75laravel:tdd-with-pest
Apply RED-GREEN-REFACTOR with Pest or PHPUnit; use factories, feature tests for HTTP, and parallel test runners; verify failures before implementation
75