Laravel Verification

CommunityPopular

affaan-m

laravel-verification

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.

Overview

Publisher	affaan-m
Repository	`ECC`
Skill name	`laravel-verification`
Stars	261.1K
Forks	39.1K
Bundled files	Instructions only
License	MIT
Links	Skill source Repository Homepage

Markdown instructions
A SKILL.md file the model loads on demand, so it only costs tokens when a request actually matches.
Works with any LLM
AI skills are plain Markdown, not provider-specific code, so this works with GPT, Claude, Gemini, Grok, or a local model.
Self-contained
Everything the model needs lives in the instructions — no extra files to sync.
Open source
Published by affaan-m on GitHub. Read the source before you install it.

Installation

Install the Laravel Verification AI skill in TypingMind to use it with any LLM, or drop it into another agent that reads SKILL.md.

Install in TypingMind

TypingMind installs a skill straight from its GitHub folder — it reads SKILL.md, bundles the resource files, and stores the result locally.

Open the app and go to Plugins → Skills.
Choose "Install from GitHub".
Paste the skill folder URL below and confirm.
Enable the skill in any chat where you want it available.

Plugins → Skills → Add skill → From GitHub URL, then paste the folder URL and press Continue.

Install in another agent

Any agent that reads the Agent Skills format can use this skill — copy the folder into that agent's skills directory.

Claude Code — .claude/skills

git clone --depth 1 https://github.com/affaan-m/ECC.git /tmp/ECC
mkdir -p .claude/skills
cp -r /tmp/ECC/docs/es/skills/laravel-verification .claude/skills/laravel-verification

Restart Claude Code after copying so it picks up the new skill.

Use it in TypingMind

Enable Laravel Verification in any TypingMind chat and the model takes it from there. Its name and description sit in the system prompt, and the moment a request matches, the model loads the full instructions itself — you never invoke it by hand, and it costs no tokens until it is actually used.

The model loads Laravel Verification on its own as soon as a request matches it.

Works with any AI model

AI skills are plain Markdown instructions rather than provider-specific code, so Laravel Verification is not tied to the model it was written for. Install it once in TypingMind and use it with GPT-5, Claude, Gemini, Grok, DeepSeek, Mistral, Llama, or a local model you run yourself — all on your own API keys.

Loaded only when it is needed
The system prompt carries just the name and description. The instructions are fetched on the first matching request, so an idle skill costs nothing.
Switch models mid-chat
Because the skill is instructions rather than code, changing model does not break it — the next model reads the same SKILL.md.

Skill instructions

This is the SKILL.md content the model loads. Read it before installing — a skill is instructions your model will follow.

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

bash
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:

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

Fase 1.5: Composer y Autoload

bash
composer validate
composer dump-autoload -o

Fase 2: Linting y Análisis Estático

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

Si el proyecto usa Psalm en lugar de PHPStan:

bash
vendor/bin/psalm

Fase 3: Pruebas y Cobertura

bash
php artisan test

Cobertura (CI):

bash
XDEBUG_MODE=coverage php artisan test --coverage

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

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

Fase 4: Seguridad y Verificación de Dependencias

bash
composer audit

Fase 5: Base de Datos y Migraciones

bash
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

bash
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

bash
php artisan schedule:list
php artisan queue:failed

Si se usa Horizon:

bash
php artisan horizon:status

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

bash
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).

bash
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:

bash
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:

bash
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

Frequently asked questions

What does the Laravel Verification AI skill do?

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.

Why use Laravel Verification on TypingMind?

Because you install it once and use it with any model. Laravel Verification is plain Markdown rather than provider-specific code, so the same skill runs on GPT-5, Claude, Gemini, Grok, or a local model — and you can switch model mid-chat without it breaking. TypingMind runs on your own API keys, so you pay providers directly instead of a per-seat subscription, and your skills and chats stay in your own storage.

How do I install Laravel Verification in TypingMind?

Open Plugins → Skills → Install from GitHub in TypingMind and paste https://github.com/affaan-m/ECC/tree/main/docs/es/skills/laravel-verification. TypingMind reads its SKILL.md and installs it as a skill you can enable per chat.

Which AI models can use Laravel Verification?

Any model you connect in TypingMind. AI skills are plain Markdown instructions rather than provider-specific code, so GPT, Claude, Gemini, Grok, and local models can all load this skill when a request matches it.

How many AI models can I use with Laravel Verification?

As many as you like. As long as a model supports skills, you can use Laravel Verification with it — GPT, Claude, Gemini, Grok, DeepSeek, Mistral, Llama and more — all on TypingMind with your own API keys.

Is the Laravel Verification AI skill free?

Yes. It is published on GitHub by affaan-m under the MIT license. You only pay your own AI provider for the tokens you use.

What are AI skills?

An AI skill is a reusable instruction bundle that teaches an AI model how to do one specific task. It follows the open Agent Skills format: a SKILL.md file with a name and description, plus any scripts, templates or reference files the model may need. The model reads the instructions only when your request matches the skill, so an installed skill costs nothing until it is used.

How are AI skills different from plugins or MCP servers?

A plugin or MCP server gives a model new tools to call — code that runs somewhere and returns a result. An AI skill gives the model knowledge and process instead: how to approach a task, which steps to follow, what good output looks like. Skills are plain Markdown, so they need no server, no API key and no runtime, and they work with any model.

View all

Writing Plans

obra

CommunityPopular

Use when you have a spec or requirements for a multi-step task, before touching code

Ask Matt

Ask which skill or flow fits your situation. A router over the skills in this repo.

Code Review

Review the changes since a fixed point (commit, branch, tag, or merge-base) along two axes: Standards (does the code follow this repo's documented coding standards?) and Spec (does the code match what…

Codebase Design

Shared vocabulary for designing deep modules. Use when the user wants to design or improve a module's interface, find deepening opportunities, decide where a seam goes, make code more testable or…

Overview

Installation

Install in TypingMind

Install in another agent

Use it in TypingMind

Works with any AI model

Skill instructions

Bucle de Verificación Laravel

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

Fase 3: Pruebas y Cobertura

Fase 4: Seguridad y Verificación de Dependencias

Fase 5: Base de Datos y Migraciones

Fase 6: Preparación de Build y Despliegue

Fase 7: Verificaciones de Cola y Scheduler

Ejemplos

Frequently asked questions

Related AI Skills

Set up your own AI workspace now