What does this skill do?

The Laravel Skill Verification runs a comprehensive verification loop for Laravel projects, covering seven sequential phases: environment and Composer checks, linting with Pint, static analysis with PHPStan, tests with code coverage, security audit, migration review, and build preparation for deployment. If any phase fails, the process stops immediately so you can correct the error before continuing.

Before Submitting a Pull Request
Check the environment, linting, tests, and security before opening a PR in your Laravel repository.
After a refactor
Run the entire pipeline after major refactorings or dependency updates.
Pre-deployment to production
Check migrations, review configurations, routes, and views, and verify queues before deploying.
Security Audit
Run `composer audit` to detect known vulnerabilities in the project's dependencies.

Usage examples

🔀 Pre-PR Verification
Please review my Laravel project before opening a pull request: run linting, tests, and a security audit.
🚀 Complete deployment pipeline
Run the entire Laravel verification pipeline and prepare the project for deployment to production.
🧪 Tests covered by insurance
Run the tests for my Laravel project with CI-style code coverage.
🔒 Audit of Government Agencies
Run `composer audit` and check for vulnerabilities in my Laravel project's dependencies.

Features

7-phase pipeline Environment, linting, static analysis, testing, security, migrations, and sequential builds.
Halt on Errors If a phase fails, the process stops immediately and displays the specific error so it can be corrected.
Linting and static analysis Integrate Pint for code styling and PHPStan or Psalm for in-depth static analysis.
Test Coverage in CI Supports XDEBUG_MODE=coverage to generate coverage reports in continuous integration pipelines.
Build Preparation Cache settings, routes, and views using `optimize:clear`, `config:cache`, `route:cache`, and `view:cache`.

Frequently asked questions

Yes. The skill executes native Laravel commands such as `php artisan`, `composer`, and `vendor/bin/pint`, so you need a working Laravel environment on your machine.
By default, it runs PHPStan (vendor/bin/phpstan analyse), but it also supports Psalm as an alternative if you have it configured in the project.
The process stops immediately at the stage where the error occurred and displays the specific error (syntax error, failed test, vulnerability, or migration issue) so you can correct it before continuing.
Yes. The skill includes an example of a complete CI-style pipeline with test coverage, security auditing, and caching of configurations, routes, and views.
Laravel Testing — Quality and Deployment Pipeline with Claude AI

¿Prefieres escuchar el contenido? Genera la narración de audio con un clic.