Agent skill · software engineering · affaan-m
laravel-verification
Verification loop for Laravel projects: env checks, linting, static analysis, tests with coverage, security scans, and deployment readiness. Use when verifying a Laravel project before merge or deploy — lint, static analysis, tests, coverage, security.
Why this skill is useful
Adds a comprehensive verification script for Laravel projects that includes environment checks, linting, testing, security scans, and deployment readiness, which the AI cannot generate from general knowledge.
What it needs
Requires composer, php installed locally. About 2k tokens when loaded. Last updated 2026-08-06. 238,342 stars on the source repository.
What this skill does
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 Verify .env is present and required keys exist Confirm APPDEBUG=false for production environments Confirm APPENV matches the target deployment (production, staging) If using Laravel Sail locally: Phase 1.5: Composer and Autoload Phase 2: Linting and Static Analysis If your project uses Psalm instead of PHPStan: Phase 3: Tests and Coverage Coverage (CI): CI example (format -> static analysis -> tests): Phase 4: Security and Dependency Checks Phase 5: Database and Migrations Review destructive migrations carefully Ensure migration filenames follow YmdHis (e.g., 20250314154210createorderstable.php) and describe the change clearly Ensure rollbacks are possible Verify down() methods and avoid irreversible data loss without explicit backups Phase 6: Build and Deployment Readiness Ensure cache warmups succeed in production configuration Verify queue workers and scheduler are configured Confirm storage/ and bootstrap/cache/ are writable in the target environment Phase 7: Queue and Scheduler Checks If Horizon is used: If queue:monitor is available, use it to check backlog without processing jobs: Active verification (staging only): dispatch a no-op job to a dedicated …
How to use it
Reference it in AdaL, Claude Code, Cursor or any coding agent — nothing to install:
@skills affaan-m/laravel-verification--3fccc5