Cuándo Usar
Antes de abrir un pull request para un proyecto Laravel
affaan-m/ECC
Bucle de verificación para proyectos Laravel: verificaciones de entorno, linting, análisis estático, pruebas con cobertura, escaneos de seguridad y preparación para despliegue.
npx skills add https://github.com/affaan-m/ECC --skill "docs/es/skills/laravel-verification"Source checked Jul 28, 2026·Refresh due Oct 26, 2026
Reorganized from the pinned upstream SKILL.md
Ejecutar antes de PRs, después de cambios importantes y antes del despliegue.
npx skills add https://github.com/affaan-m/ECC --skill "docs/es/skills/laravel-verification"The pinned source contains enough sections and task detail for a source-grounded deep guide; automated content is still not an independent test.
682 source words · 11 usable sections
Documentation workflow
Sections are extracted automatically from the pinned SKILL.md and link back to the source.
Antes de abrir un pull request para un proyecto Laravel
Ejecutar las fases secuencialmente desde las verificaciones de entorno hasta la preparación para despliegue, de modo que cada capa construya sobre la anterior.
Si se usa Laravel Sail localmente:
Review the “Fase 1.5: Composer y Autoload” section in the pinned source before continuing.
Si el proyecto usa Psalm en lugar de PHPStan:
SkillSignal prompt templates
These prompts were written by SkillSignal from the source structure; they are not upstream text.
Source-grounded prompt
Use for a documentation task while explicitly checking the source sections.
Use laravel-verification for this documentation task: [task]. Inputs and constraints: [details]. Work through these pinned SKILL.md sections: “Cuándo Usar”, “Cómo Funciona”, “Fase 1: Verificaciones de Entorno”, “Fase 1.5: Composer y Autoload”, “Fase 2: Linting y Análisis Estático”. Cite the concrete requirements that shape each step, do not invent capabilities absent from the source, and verify the result against: [acceptance criteria].
Documentation checklist
The source section “Cuándo Usar” has been checked.
The source section “Cómo Funciona” has been checked.
The source section “Fase 1: Verificaciones de Entorno” has been checked.
The source section “Fase 1.5: Composer y Autoload” has been checked.
Choose a different workflow
Verification loop for Laravel projects: env checks, linting, static analysis, tests with coverage, security scans, and deployment readiness.
A separate implementation from affaan-m/ECC; compare its source, maintenance signals, and permission requirements.
Open source detailVerification loop for Laravel projects: env checks, linting, static analysis, tests with coverage, security scans, and deployment readiness.
A separate implementation from affaan-m/ECC; compare its source, maintenance signals, and permission requirements.
Open source detailVerification loop for Laravel projects: env checks, linting, static analysis, tests with coverage, security scans, and deployment readiness.
A separate implementation from affaan-m/ECC; compare its source, maintenance signals, and permission requirements.
Open source detailFAQ
Ejecutar antes de PRs, después de cambios importantes y antes del despliegue.
The source record exposes this install command: npx skills add https://github.com/affaan-m/ECC --skill "docs/es/skills/laravel-verification". Inspect the command and pinned source before running it.
Quality breakdown
Based on traceable docs and repository signals; stars are not treated as quality.
Compare before choosing
These links are selected from shared tasks, functions, stacks, platforms, and same-name variants. Compare the source owner, documentation, permissions, and maintenance signals.
Verification loop for Laravel projects: env checks, linting, static analysis, tests with coverage, security scans, and deployment readiness.
Verification loop for Laravel projects: env checks, linting, static analysis, tests with coverage, security scans, and deployment readiness.
Verification loop for Laravel projects: env checks, linting, static analysis, tests with coverage, security scans, and deployment readiness.
Review laravel-verification's use cases, installation, workflow, and original source instructions.
Ejecutar antes de PRs, después de cambios importantes y antes del despliegue.
php -v
composer --version
php artisan --version
.env esté presente y que las claves requeridas existanAPP_DEBUG=false para entornos de producciónAPP_ENV coincida con el despliegue objetivo (production, staging)Si se usa Laravel Sail localmente:
./vendor/bin/sail php -v
./vendor/bin/sail artisan --version
composer validate
composer dump-autoload -o
vendor/bin/pint --test
vendor/bin/phpstan analyse
Si el proyecto usa Psalm en lugar de PHPStan:
vendor/bin/psalm
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
composer audit
php artisan migrate --pretend
php artisan migrate:status
Y_m_d_His_* (ej. 2025_03_14_154210_create_orders_table.php) y describan el cambio claramentedown() y evitar la pérdida irreversible de datos sin copias de seguridad explícitasphp artisan optimize:clear
php artisan config:cache
php artisan route:cache
php artisan view:cache
storage/ y bootstrap/cache/ sean escribibles en el entorno objetivophp 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.
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