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 using Laravel Sail locally:

./vendor/bin/sail php -v
./vendor/bin/sail artisan --ve…