laravel-verification

Verify Laravel environment, code quality, tests, security, and deployment readiness.

1|Updated Mar 3, 2026
One-click install
npx skills add https://github.com/samymity/bridge-ventures-backend --skill laravel-verification-samymity
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: laravel-verification
Source: https://github.com/samymity/bridge-ventures-backend/tree/main/.claude/skills/laravel-verification
Command: npx skills add https://github.com/samymity/bridge-ventures-backend --skill laravel-verification-samymity

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

It solves the risk of breaking a Laravel application by ensuring environment correctness, code quality, test/coverage integrity, security posture, and deployment readiness before merges and releases.

Core Features & Use Cases

  • Sequential verification phases: Runs environment checks, Composer validation, linting/static analysis, tests with coverage, security/dependency audits, migration safety reviews, and build/deploy readiness in a gated order.
  • Quality gates before costly work: Stops immediately if environment and Composer checks fail, and insists on clean lint/static analysis before full tests.
  • Release-focused operational checks: Verifies caches, storage writability, schedule listing, failed queue state, and optional queue healthcheck execution for staging.

Quick Start

Run the full Laravel verification loop by executing the phases in order: environment checks, Composer validate and autoload dump, pint and phpstan, XDEBUG_MODE=coverage tests, composer audit, migrate --pretend plus migrate status, and deployment readiness commands including caches and schedule/queue checks.

Frequently Asked Questions about laravel-verification

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
What is the best way to verify Laravel deployment readiness before merging?

Laravel deployment readiness is verified through sequential phases: environment checks, Composer validation, linting/static analysis, coverage-enabled testing, security audits, and migration safety reviews.

How do I run a security audit and static analysis check for my Laravel application?

Run a Laravel security audit and static analysis by executing Composer audit alongside PHPStan and Pint. Quality gates ensure environment correctness before proceeding to tests and deployment readiness checks.

Can I check Laravel migration safety before deploying to production?

Yes, Laravel migration safety is checked using migrate --pretend and migrate status commands. This reviews pending database changes and validates migration state before applying them to a production environment.

Does Laravel CI pipeline testing require coverage and queue scheduler validation?

Laravel CI pipeline testing requires XDEBUG_MODE=coverage for test coverage and validates queue scheduler health. Schedule listing, failed queue state checks, and optional queue healthcheck execution confirm staging and production readiness.

Why does my Laravel verification workflow stop before running tests?

Laravel verification stops before tests if environment and Composer checks fail, or if lint/static analysis via Pint and PHPstan detects issues. These quality gates prevent executing costly testing phases on broken code.