laravel-quality-checks

Run Pint, PHPStan, Psalm, and JS linters for Laravel projects.

Updated Jun 8, 2025

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

Ready to run

npx skills add https://github.com/noartem/kawa --skill laravel-quality-checks-noartem

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: laravel-quality-checks
Source: https://github.com/noartem/kawa/tree/main/ui/.ai/skills/laravel-quality-checks
Command: npx skills add https://github.com/noartem/kawa --skill laravel-quality-checks-noartem

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Unified Laravel quality gates across Pint, static analyzers (PHPStan/Psalm), optional Insights, and JS linters to ensure clean, production-ready code.

Core Features & Use Cases

Unified checks: runs Pint, PHPStan, Psalm, Insights (optional), and linting for Laravel projects.
Sail and non-Sail support: works with Sail-based and non-Sail Laravel environments.
Pre-merge validation: integrates into CI pipelines to gate PRs with consistent quality gates.

Quick Start

Run the Laravel quality checks across Pint, PHPStan/Psalm, Insights (optional), and JS linters to validate a 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 run Laravel quality checks across Pint, PHPStan, and Psalm together?▼

Laravel quality checks can be automated across Pint, PHPStan, and Psalm by executing them via vendor/bin commands to deliver consistent project hygiene results and gate builds for production readiness.

Can I use these Laravel quality gates with a Sail-based environment?▼

Yes, these Laravel quality gates support both Sail-based and non-Sail Laravel environments, applying unified checks across static analyzers and linters to validate project hygiene consistently across different setups.

What's the best way to automate pre-merge validation for a Laravel project?▼

Automating pre-merge validation involves running unified quality gates across Pint, PHPStan, Psalm, and JS linters to gate pull requests with consistent checks before merging into the main branch.

Do I need to install PHPStan and Psalm before running these Laravel quality checks?▼

Yes, you must install Pint, PHPStan, and Psalm via vendor/bin commands to execute the quality checks. Insights is optional and can be added for additional code analysis if desired.

What problem does combining multiple static analyzers solve for Laravel builds?▼

Combining multiple static analyzers solves the problem of fragmented quality validation by creating unified quality gates across Pint, PHPStan, Psalm, and JS linters to ensure clean, production-ready code.

Does this quality check workflow include JavaScript linting for Laravel projects?▼

Yes, the automated Laravel quality checks include JS linters alongside PHP static analysis tools like PHPStan and Psalm to maintain full-stack project hygiene across both PHP and JavaScript code.