laravel:quality-checks

Name: laravel:quality-checks
Availability: InStock
Author: Meistro

Run automated quality gates for Laravel projects with Pint, PHPStan, and frontend linters.

1|Updated Sep 22, 2025

Search Tags:#testing #static analysis #linting #laravel #phpstan #pint #quality checks

Ready to run

npx skills add https://github.com/meistro57/chat_bridge --skill laravel-quality-checks

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: laravel:quality-checks
Source: https://github.com/meistro57/chat_bridge/tree/main/.claude/skills/quality-checks
Command: npx skills add https://github.com/meistro57/chat_bridge --skill laravel-quality-checks

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) components.

What problem does it solve?

This Skill ensures your Laravel project adheres to high coding standards and passes essential quality gates before code merges or deployment, preventing technical debt and improving maintainability.

Core Features & Use Cases

PHP Linting & Formatting: Uses Pint to enforce consistent code style.
Static Analysis: Integrates with PHPStan or Psalm to catch bugs and type errors.
Testing: Runs your project's test suite, including parallel execution.
Frontend Checks: Supports linting and type checking for JavaScript/TypeScript.
Use Case: Before merging a new feature, run this Skill to automatically verify code style, catch potential bugs with static analysis, and ensure all tests pass, guaranteeing a clean codebase.

Quick Start

Execute all automated quality checks for the current Laravel project.

Frequently Asked Questions about laravel:quality-checks

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

FAQPage Schema

How do I automate Laravel code quality checks for PHP linting and static analysis?▼

To automate Laravel code quality checks, use a unified script that runs Pint for PHP linting and PHPStan or Psalm for static analysis. This ensures consistent code style and catches type errors before merging.

What's the best way to run static analysis and linting in a Laravel CI/CD pipeline?▼

The best way to run static analysis and linting in a Laravel CI/CD pipeline is using automated quality gates. This integrates PHPStan or Psalm and Pint into your workflow, supporting both Sail and non-Sail environments for seamless deployment checks.

Does this automated quality check tool support Laravel Sail environments?▼

Yes, the automated quality check tool supports both Sail and non-Sail Laravel environments. This ensures seamless integration of PHP linting, static analysis, and testing into your existing CI/CD pipelines regardless of your setup.

Can I run frontend linting and type checking alongside PHP static analysis in Laravel?▼

Yes, you can run frontend linting and type checking alongside PHP static analysis in Laravel. The automated quality checks support JavaScript and TypeScript linters, ensuring code quality across both backend and frontend workflows.

How do I run Laravel test suites with parallel execution during quality checks?▼

Run Laravel test suites with parallel execution by including them in your automated quality checks. This runs your tests alongside Pint linting and PHPStan static analysis, verifying code style, catching bugs, and ensuring all tests pass before deployment.

Why should I use PHPStan or Psalm for Laravel static analysis before merging code?▼

Use PHPStan or Psalm for Laravel static analysis before merging to catch bugs and type errors early. Integrating these tools as quality gates prevents technical debt, improves maintainability, and ensures your project adheres to high coding standards.