laravel-static-analysis

Automate static analysis and formatting for Laravel 12 by orchestrating Pint, Larastan, Rector, and Pest into a unified quality gate pipeline. This ensures code meets strict type safety and formatting standards before merging.

Manage technical debt in a legacy PHP codebase using shrinking baselines. This approach structures your static analysis to ignore existing errors while preventing new code from introducing additional type-safety violations.

Yes, you can integrate PHPStan and Rector into a Laravel CI/CD pipeline. The skill automates these tools alongside Pint and Pest to enforce automated code quality verification on every feature branch before code review.

This static analysis workflow explicitly supports PHP 8.3 applications. It applies strict quality gates, type checking, and automated refactoring standards tailored for Laravel 12 and PHP 8.3+ environments.

Enforce type-safe codebases and consistent formatting by running the full quality gate pipeline before code review. This automatically verifies type safety using Larastan and formatting using Pint to satisfy project standards.

Use shrinking baselines when adding static analysis to an existing Laravel project to avoid being overwhelmed by legacy code debt. It isolates existing violations, allowing you to enforce strict rules on new code while gradually reducing the baseline.