php-quality

To enforce strict types and PSR-12 compliance during PHP code review, validate that every file declares `strict_types=1` and check formatting, whitespace, and brace style against PSR-12 standards. This prevents silent type coercion and ensures consistent structural conventions across your codebase.

For modern PHP code quality in versions 8.0 through 8.2, apply enums, readonly properties, match expressions, null-safe operators, and named arguments. Using these features ensures your codebase follows current language standards and avoids deprecated structural patterns.

Yes, this PHP quality review works with Laravel and Symfony framework idioms. It validates framework-specific patterns including Eloquent scopes, collection usage, service container binding, Symfony DI attributes, and event dispatchers when those framework signals are present in your code.

To configure PHPStan, Psalm, PHP-CS-Fixer, and Rector for static analysis and code style, use tooling-aware references that guide CI expectations and configuration setup. This ensures your automated quality gates align with strict typing and modern PHP standards.

Your PHP code fails strict typing checks during static analysis if files are missing `declare(strict_types=1)` at the top. This declaration prevents silent type coercion, and without it, static analysis tools flag type mismatches that would otherwise pass silently during runtime.

Yes, you can use Rector to automate modern PHP code quality fixes for PSR-12. Rector serves as a tooling-aware reference that helps configure automated upgrades and structural fixes, ensuring your code aligns with strict typing and modern language conventions.