Verification loop for Laravel projects: env checks, linting, static analysis, tests with coverage, security scans, and deployment readiness. USE WHEN preparing a Laravel PR, after major refactors or dependency upgrades, or running pre-deploy lint-test-security-readiness gates.
Verification loop for Laravel projects: env checks, linting, static analysis, tests with coverage, security scans, and deployment readiness. USE WHEN preparing a Laravel PR, after major refactors or dependency upgrades, or running pre-deploy lint-test-security-readiness gates.
origin
ECC
cluster
php-laravel
version
1.0.0
Laravel Verification Loop
Run before PRs, after major changes, and pre-deploy.
When to Use
Before opening a pull request for a Laravel project
After major refactors or dependency upgrades
Pre-deployment verification for staging or production
Running full lint -> test -> security -> deploy readiness pipeline
How It Works
Run phases sequentially from environment checks through deployment readiness so each layer builds on the last.
Environment and Composer checks gate everything else; stop immediately if they fail.
Linting/static analysis should be clean before running full tests and coverage.
Security and migration reviews happen after tests so you verify behavior before data or release steps.
Build/deploy readiness and queue/scheduler checks are final gates; any failure blocks release.
Phase 1: Environment Checks
php -v
composer --version
php artisan --version
Verify .env is present and required keys exist
Confirm APP_DEBUG=false for production environments
Confirm APP_ENV matches the target deployment (production, staging)
If queue:monitor is available, use it to check backlog without processing jobs:
php artisan queue:monitor default --max=100
Active verification (staging only): dispatch a no-op job to a dedicated queue and run a single worker to process it (ensure a non-sync queue connection is configured).
