laravel-verification

Runs a phased verification pipeline for Laravel projects covering linting, tests, security, and deployment readiness.

1|Updated Oct 11, 2025
One-click install
npx skills add https://github.com/ibytechaos/claude --skill laravel-verification-ibytechaos
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: laravel-verification
Source: https://github.com/ibytechaos/claude/tree/main/plugins/everything-claude-code/skills/laravel-verification
Command: npx skills add https://github.com/ibytechaos/claude --skill laravel-verification-ibytechaos

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Laravel teams often ship changes without a consistent pre-release checklist, leading to broken deployments, missed security vulnerabilities, and failed migrations. This Skill provides a structured, sequential verification loop that gates pull requests and deployments behind environment, code quality, test, security, and infrastructure checks. ## Core Features & Use Cases - Phased Verification Pipeline: Runs environment checks, Composer validation, Pint linting, PHPStan/Psalm static analysis, tests with coverage, and Composer security audits in a strict order where each phase gates the next. - Deployment Readiness Gates: Validates migrations with migrate --pretend, warms config/route/view caches, and confirms queue workers, schedulers, and Horizon status before release. - Use Case: Before merging a pull request after a major dependency upgrade, run the full loop to confirm Pint passes, PHPStan is clean, tests pass with coverage, composer audit reports no vulnerabilities, and cache warmups succeed in production configuration. ## Quick Start Run the Laravel verification loop on my project before I open a pull request and report any failures by phase.

Frequently Asked Questions about laravel-verification

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I verify a Laravel project before deployment?

Run a phased pipeline: check PHP and Composer versions, validate composer.json, run Pint and PHPStan, execute tests with coverage, run composer audit, preview migrations with migrate --pretend, and warm config, route, and view caches. Each phase gates the next, so stop on the first failure.

How to run Laravel tests with code coverage in CI?

Use XDEBUG_MODE=coverage php artisan test --coverage to generate coverage reports in CI. Run it after Pint formatting checks and PHPStan static analysis so style and type issues are caught before the slower test suite executes.

Should I use PHPStan or Psalm for Laravel static analysis?

Both work for Laravel static analysis; the verification loop supports either. Run vendor/bin/phpstan analyse if your project uses PHPStan, or vendor/bin/psalm if it uses Psalm, depending on which tool is already configured in the project.

Can I test Laravel queue workers without processing real jobs?

Yes, on staging only. Dispatch a no-op healthcheck job to a dedicated queue with a non-sync connection, then run php artisan queue:work --once --queue=healthcheck and verify the expected side effect. Never run this on production.

Why does Laravel deployment fail after config:cache?

Cache warmups fail when environment variables are missing, storage or bootstrap/cache directories are not writable, or closures exist in route files. Verify APP_ENV and required .env keys, confirm directory permissions, and run optimize:clear before re-caching.