Now liveThe Skillselion MCP - thousands of ranked skills, loaded into your agent mid-task. No install.Get it →
affaan-m avatar

Laravel Verification

  • 1.4k installs
  • 238k repo stars
  • Updated August 5, 2026
  • affaan-m/ecc

This is a copy of laravel-verification by affaan-m - installs and ranking accrue to the original listing.

laravel-verification is a Claude Code skill that runs a sequential Laravel verification loop across environment, lint, test, security, migration, and deploy-readiness phases for developers who need confidence before pull

About

laravel-verification is an ECC skill that runs a complete Laravel quality gate before pull requests, major refactors, or production deploys. The loop spans eight sequential phases: environment and Artisan checks, Composer validation, Pint linting, PHPStan or Psalm static analysis, PHPUnit tests with optional Xdebug coverage, composer audit security scans, migration pretend runs with rollback review, and deployment readiness including config, route, and view cache warmups plus queue and scheduler checks. Each phase gates the next—failed environment or Composer checks stop the pipeline before expensive test runs. The skill documents Sail-compatible commands, Horizon status checks, queue:monitor backlog inspection, and a staging-only queue healthcheck job pattern. CI examples chain pint --test, phpstan analyse, and coverage-enabled php artisan test. Developers reach for laravel-verification when Laravel changes need proof that lint, tests, security, migrations, and release caches all pass together.

  • Sequential verification pipeline: environment checks → linting → static analysis → tests with coverage → security scans
  • Hard gates at each layer — environment and Composer failures stop the pipeline immediately
  • Covers PHP version, Composer validation, .env sanity, linting, PHPUnit with coverage, security review, migration checks,
  • Supports both native PHP and Laravel Sail environments
  • Designed to run before PRs, after major refactors, and pre-deploy

Laravel Verification by the numbers

  • 1,383 all-time installs (skills.sh)
  • +84 installs in the week ending Aug 5, 2026 (Skillselion tracking)
  • Data as of Aug 5, 2026 (Skillselion catalog sync)
npx skills add https://github.com/affaan-m/ecc --skill laravel-verification

Add your badge

Show developers this skill is listed on Skillselion. Paste this into your README.

Listed on Skillselion
Installs1.4k
repo stars238k
Last updatedAugust 5, 2026
Repositoryaffaan-m/ecc

What checks should Laravel run before deploy?

Run a complete verification loop on Laravel projects before opening pull requests or deploying.

Who is it for?

Laravel developers and platform engineers who need a repeatable pre-PR or pre-deploy gate covering lint, static analysis, tests, security, migrations, and cache warmups.

Skip if: Teams not using Laravel or projects that only need a single isolated PHPUnit run without lint, audit, migration, or deploy-readiness checks should skip laravel-verification.

When should I use this skill?

A Laravel pull request or production deploy is imminent and the team wants the full lint, test, security, migration, and cache-readiness pipeline executed sequentially.

What you get

Sequential phase pass/fail report, lint and static-analysis results, test coverage output, security audit log, and deployment-readiness confirmation

  • Phase-by-phase verification log
  • Test and coverage results
  • Deploy-readiness checklist

By the numbers

  • Defines 8 sequential verification phases from environment checks through queue health
  • Documents CI chaining Pint, PHPStan, and coverage-enabled php artisan test

Files

SKILL.mdMarkdownGitHub ↗

Bucle de Verificación Laravel

Ejecutar antes de PRs, después de cambios importantes y antes del despliegue.

Cuándo Usar

  • Antes de abrir un pull request para un proyecto Laravel
  • Después de refactorizaciones importantes o actualizaciones de dependencias
  • Verificación previa al despliegue para staging o producción
  • Ejecutar el pipeline completo de lint -> prueba -> seguridad -> preparación para despliegue

Cómo Funciona

  • Ejecutar las fases secuencialmente desde las verificaciones de entorno hasta la preparación para despliegue, de modo que cada capa construya sobre la anterior.
  • Las verificaciones de entorno y Composer son requisitos previos para todo lo demás; detener inmediatamente si fallan.
  • El linting/análisis estático debe estar limpio antes de ejecutar pruebas completas y cobertura.
  • Las revisiones de seguridad y migraciones ocurren después de las pruebas para verificar el comportamiento antes de los pasos de datos o lanzamiento.
  • La preparación de build/despliegue y las verificaciones de cola/scheduler son los últimos filtros; cualquier fallo bloquea el lanzamiento.

Fase 1: Verificaciones de Entorno

php -v
composer --version
php artisan --version
  • Verificar que .env esté presente y que las claves requeridas existan
  • Confirmar APP_DEBUG=false para entornos de producción
  • Confirmar que APP_ENV coincida con el despliegue objetivo (production, staging)

Si se usa Laravel Sail localmente:

./vendor/bin/sail php -v
./vendor/bin/sail artisan --version

Fase 1.5: Composer y Autoload

composer validate
composer dump-autoload -o

Fase 2: Linting y Análisis Estático

vendor/bin/pint --test
vendor/bin/phpstan analyse

Si el proyecto usa Psalm en lugar de PHPStan:

vendor/bin/psalm

Fase 3: Pruebas y Cobertura

php artisan test

Cobertura (CI):

XDEBUG_MODE=coverage php artisan test --coverage

Ejemplo de pipeline CI (formato -> análisis estático -> pruebas):

vendor/bin/pint --test
vendor/bin/phpstan analyse
XDEBUG_MODE=coverage php artisan test --coverage

Fase 4: Seguridad y Verificación de Dependencias

composer audit

Fase 5: Base de Datos y Migraciones

php artisan migrate --pretend
php artisan migrate:status
  • Revisar cuidadosamente las migraciones destructivas
  • Asegurarse de que los nombres de archivo de migración sigan el formato Y_m_d_His_* (ej. 2025_03_14_154210_create_orders_table.php) y describan el cambio claramente
  • Asegurarse de que los rollbacks sean posibles
  • Verificar los métodos down() y evitar la pérdida irreversible de datos sin copias de seguridad explícitas

Fase 6: Preparación de Build y Despliegue

php artisan optimize:clear
php artisan config:cache
php artisan route:cache
php artisan view:cache
  • Asegurarse de que los warmups de caché tengan éxito en la configuración de producción
  • Verificar que los workers de cola y el scheduler estén configurados
  • Confirmar que storage/ y bootstrap/cache/ sean escribibles en el entorno objetivo

Fase 7: Verificaciones de Cola y Scheduler

php artisan schedule:list
php artisan queue:failed

Si se usa Horizon:

php artisan horizon:status

Si queue:monitor está disponible, usarlo para verificar el backlog sin procesar jobs:

php artisan queue:monitor default --max=100

Verificación activa (solo staging): despachar un job no-op a una cola dedicada y ejecutar un solo worker para procesarlo (asegurarse de que esté configurada una conexión de cola que no sea sync).

php artisan tinker --execute="dispatch((new App\\Jobs\\QueueHealthcheck())->onQueue('healthcheck'))"
php artisan queue:work --once --queue=healthcheck

Verificar que el job produjera el efecto secundario esperado (entrada de log, fila en tabla de healthcheck o métrica).

Ejecutar esto solo en entornos que no sean producción donde procesar un job de prueba sea seguro.

Ejemplos

Flujo mínimo:

php -v
composer --version
php artisan --version
composer validate
vendor/bin/pint --test
vendor/bin/phpstan analyse
php artisan test
composer audit
php artisan migrate --pretend
php artisan config:cache
php artisan queue:failed

Pipeline estilo CI:

composer validate
composer dump-autoload -o
vendor/bin/pint --test
vendor/bin/phpstan analyse
XDEBUG_MODE=coverage php artisan test --coverage
composer audit
php artisan migrate --pretend
php artisan optimize:clear
php artisan config:cache
php artisan route:cache
php artisan view:cache
php artisan schedule:list

Related skills

How it compares

Pick laravel-verification over generic testing skills when you need Laravel-specific gates—Pint, PHPStan, migrate --pretend, and Artisan cache warmups—in one ordered pipeline.

FAQ

What phases does laravel-verification run?

laravel-verification runs eight sequential phases: environment and Artisan checks, Composer validation, Pint linting, PHPStan or Psalm analysis, PHPUnit tests with optional coverage, composer audit, migration pretend runs, and deployment readiness including config, route, view ca

When should laravel-verification stop the pipeline?

laravel-verification stops immediately if environment or Composer checks fail, before running full tests. Lint and static analysis must be clean before coverage runs, and any failure in migration review, cache warmup, or queue health blocks release.

Testing & QAbackendtesting

This week in AI coding

Five minutes, every Monday - the tools, releases and tactics for developers.

unsubscribe anytime.