laravel-verification

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

Updated Mar 25, 2026
One-click install
npx skills add https://github.com/Femad-6/my-skills --skill laravel-verification-femad-6
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: laravel-verification
Source: https://github.com/Femad-6/my-skills/tree/main/.github/skills/laravel-verification
Command: npx skills add https://github.com/Femad-6/my-skills --skill laravel-verification-femad-6

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Laravel teams often ship changes without a consistent pre-release checklist, leading to broken deployments, failed migrations, or security vulnerabilities slipping into production. This Skill provides a structured, sequential verification loop that gates every release behind environment, code quality, test, security, and deployment 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. - Database and Migration Safety: Previews migrations with migrate --pretend, checks migration status, and enforces rollback safety before release. - Deployment Readiness: Validates config/route/view caching, queue workers, scheduler configuration, and Horizon status before go-live. - Use Case: Before opening a pull request on a Laravel application, 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 this project and report any failures in linting, tests, security audits, or deployment readiness.

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. Any failure blocks the release.

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 code quality gates pass 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 uses vendor/bin/phpstan analyse by default, but projects configured with Psalm can substitute vendor/bin/psalm at the same pipeline phase.

How do I check Laravel migrations are safe before deploying?

Run php artisan migrate --pretend to preview SQL without executing it, and php artisan migrate:status to confirm pending migrations. Review destructive changes, verify down() methods exist, and ensure rollbacks are possible before release.

Can I verify Laravel queue workers without processing real jobs?

Yes. Use php artisan queue:failed to inspect failures and queue:monitor to check backlog. On staging only, dispatch a no-op healthcheck job to a dedicated queue and process it with queue:work --once to confirm the worker pipeline functions.