laravel-verification

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

Updated Mar 18, 2026
One-click install
npx skills add https://github.com/freedom909/real-estate-saas --skill laravel-verification-freedom909
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: laravel-verification
Source: https://github.com/freedom909/real-estate-saas/tree/main/.trae/skills/laravel-verification
Command: npx skills add https://github.com/freedom909/real-estate-saas --skill laravel-verification-freedom909

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Laravel developers often ship code without a consistent pre-release checklist, leading to broken deployments, failed migrations, or security vulnerabilities discovered too late. 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 pretend mode, cache warmups (config, route, view), queue workers, and scheduler configuration before release. - Use Case: Before opening a pull request after a major refactor, run the full loop to confirm Pint formatting is clean, PHPStan reports no errors, tests pass with coverage, no vulnerable Composer dependencies exist, and migrations are reversible. ## Quick Start Run the Laravel verification loop on my project and report any failures across linting, tests, security, and 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 for formatting, PHPStan for static analysis, execute tests with coverage, audit dependencies, pretend-run migrations, 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.

PHPStan vs Psalm for Laravel static analysis?▼

Both detect type errors and bugs in Laravel code; this workflow uses vendor/bin/phpstan analyse by default but supports vendor/bin/psalm if your project already uses Psalm. Choose whichever your team has configured rather than running both.

Does this verification work with Laravel Sail?▼

Yes, environment checks support Laravel Sail by prefixing commands with ./vendor/bin/sail, such as sail php -v and sail artisan --version. The remaining phases run the same way inside the Sail container environment.

How do I check Laravel queue health without processing jobs?▼

Use php artisan queue:failed to inspect failed jobs and php artisan queue:monitor default --max=100 to check backlog without processing. On staging only, you can dispatch a no-op healthcheck job and run queue:work --once to verify active processing.

When should the Laravel verification loop not run active queue checks?▼

Active queue verification that dispatches and processes a test job should only run on non-production environments. Processing a test job in production can cause unintended side effects, so limit production checks to passive monitoring commands.