laravel-static-analysis

Automate Laravel 12 static analysis, formatting, and refactoring with Pint, Larastan, Rector, and Pest.

Updated Apr 15, 2026

Search Tags:#php #laravel #static-analysis #quality-assurance #phpstan #rector

Ready to run

npx skills add https://github.com/gab3mioni/laravel-claudecode-toolkit --skill laravel-static-analysis

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: laravel-static-analysis
Source: https://github.com/gab3mioni/laravel-claudecode-toolkit/tree/main/skills/laravel-static-analysis
Command: npx skills add https://github.com/gab3mioni/laravel-claudecode-toolkit --skill laravel-static-analysis

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) and references (resource) components.

What problem does it solve?

This skill eliminates the manual overhead of maintaining code quality in Laravel 12 projects by automating the verification of formatting, type safety, and refactoring standards.

Core Features & Use Cases

Automated Verification: Orchestrates Pint, Larastan, Rector, and Pest to ensure code meets strict quality gates before merging.
Baseline Management: Provides a structured approach to managing technical debt in legacy codebases through shrinking baselines.
Use Case: Use this skill to automatically run the full quality gate pipeline, including static analysis and type checking, to ensure a new feature branch adheres to project standards before a code review.

Quick Start

Use the laravel-static-analysis skill to run the full quality gate pipeline on the current project.

Frequently Asked Questions about laravel-static-analysis

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

FAQPage Schema

How do I automate static analysis and formatting checks for Laravel 12?▼

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.

What is the best way to manage technical debt in a legacy PHP codebase?▼

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.

Can I integrate PHPStan and Rector directly into a Laravel CI/CD pipeline?▼

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.

Does this static analysis workflow support PHP 8.3 applications?▼

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.

How do I enforce type-safe codebases and consistent formatting before a code review?▼

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.

Why use shrinking baselines when adding static analysis to an existing Laravel project?▼

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.