phpstan-fixer

PHPStan Error Fixer

Fix PHPStan static analysis errors through proper type annotations, PHPDocs, and code improvements. This skill teaches agents how to resolve errors without suppressing them, respecting the project's configured strictness level.

Core Principles

1. Never suppress errors as first resort — Fix the root cause with proper types and annotations
2. Respect user configuration — Never modify phpstan.neon settings (level, paths, parameters)
3. No silent ignoring — Never add ignoreErrors to config without explicit user approval
4. Context-aware fixes — Understand the project type (Laravel, Symfony, vanilla PHP) before proposing solutions
5. Ask before ignoring — If a legitimate ignore is needed, explain why and get user approval first
6. Don't fix third-party code — Never modify files in vendor/. Use stub files instead to override wrong types

Workflow

Step 1: Understand the Project Context

Before fixing errors, identify the project type:

# Check for Laravel
grep laravel/framework composer.json

# Check for Symfony
grep symfony/symfony composer.json

# Check for PHPStan extensions
grep phpstan composer.json

# Read PHPStan config
cat phpstan.neon

# Check project guidelines
cat AGENTS.md

Key information to extract:

• PHPStan level (0-10, or max)
• Installed PHPStan extensions (larastan, phpstan-strict-rules, etc.)
• Framework-specific helpers (Laravel IDE Helper, Symfony plugin)
• Project-specific type conventions

Step 2: Analyze the Error

PHPStan errors have this structure:

------ ----------------------------------------------
Line   /path/to/File.php
------ ----------------------------------------------
42     Parameter $user of method foo() has invalid
       type App\User.
       💡 Identifier: parameter.type
------ ----------------------------------------------

Extract:

1. Error identifier (e.g., parameter.type, missingType.return)
2. Error location (file, line number)
3. Context (what's the code trying to do?)