laravel:quality-checks

Run Pint, PHPStan, Psalm, tests, and JS linters for Laravel quality gates.

Updated Mar 30, 2026
One-click install
npx skills add https://github.com/Patkik/Multi-tenant-SaaS-Catering-V2 --skill laravel-quality-checks-patkik
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: laravel:quality-checks
Source: https://github.com/Patkik/Multi-tenant-SaaS-Catering-V2/tree/main/.agents/skills/quality-checks
Command: npx skills add https://github.com/Patkik/Multi-tenant-SaaS-Catering-V2 --skill laravel-quality-checks-patkik

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Automated, repeatable quality checks for Laravel projects by combining code style, static analysis, insights, tests, and frontend linting into a single workflow.

Core Features & Use Cases

  • Pint-based linting to enforce coding standards and formatting
  • Static analysis with PHPStan or Psalm to detect potential defects
  • Insights integration (optional) for deeper analytics and quality signals
  • Automated tests execution to verify behavior and prevent regressions
  • Frontend linting and type checks when a frontend stack is present
  • Sail and non-Sail environment compatibility for diverse workflows

Quick Start

Run the quality checks locally to validate Laravel code before handoff.

Frequently Asked Questions about laravel:quality-checks

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

FAQPage Schema
How do I run Laravel quality checks combining Pint, PHPStan, and tests?

Laravel quality checks combine Pint, PHPStan or Psalm, tests, and frontend linting into a single workflow. This unified approach enforces code style, static analysis, and behavioral testing to ensure comprehensive code quality before handoff.

What's the best way to automate PHPStan and Pint checks in a Laravel CI pipeline?

Automating Laravel CI quality gates involves running Pint for formatting and PHPStan or Psalm for static analysis alongside tests. This guarantees repeatable code quality enforcement across continuous integration and pre-merge workflows.

Does this Laravel quality gate workflow support Sail and non-Sail environments?

Yes, the Laravel quality gates are compatible with both Sail and non-Sail environments. This ensures diverse local development workflows and CI pipelines can run Pint, PHPStan, and frontend linting without environment conflicts.

Do I need frontend linting tools to run Laravel static analysis and quality checks?

Frontend linting and type checks are only required when a frontend stack is present. Core Laravel quality checks require Pint and PHPStan or Psalm, while frontend linting and insights integration remain optional.

Why combine Pint and Psalm instead of using a single Laravel code quality tool?

Combining Pint and Psalm unifies code formatting and deep static analysis within one workflow. This multi-tool strategy catches broader potential defects and enforces stricter quality gates than relying on a single tool.