Refactor PHP/Laravel code with behavior-preserving changes and PHPDoc enhancements.
npx skills add https://github.com/pekral/cursor-rules --skill class-refactoring
Please help me install this Agent Skill. Skill: class-refactoring Source: https://github.com/pekral/cursor-rules/tree/main/skills/class-refactoring Command: npx skills add https://github.com/pekral/cursor-rules --skill class-refactoring
PHP/Laravel projects often accumulate complexity and duplication, making maintenance and onboarding painful. This Skill enables safe, behavior-preserving refactoring to improve readability, consistency, and maintainability without altering external functionality.
To start refactoring, point the Skill at your PHP/Laravel project and instruct it to review the codebase for simplification and clarity.
High-intent search queries and answers about installing and using this skill.
To refactor PHP code safely, apply behavior-preserving changes that enforce SRP and DRY principles while validating all modifications against your project's existing test suite. This ensures readability and maintainability improve without altering external functionality.
Reducing code duplication in Laravel controllers and services involves analyzing the codebase to identify refactoring opportunities and applying DRY principles. This process improves maintainability and consistency while ensuring tests remain green and functionality is preserved.
Yes, you can improve PHPDoc and type hints during refactoring by applying clean, PHPDoc-enhanced changes and typed properties. This improves static analysis and maintainability across controllers, models, services, and tests without changing functionality.
Behavior-preserving refactoring relies on your existing Laravel test suite to validate that changes do not alter external functionality. It enforces tests remain green throughout the refactoring process, ensuring safe improvements to readability and consistency.
Identifying refactoring opportunities across PHP models and tests requires analyzing the codebase for simplification and clarity. The process guides developers through behavior-preserving changes that enforce SRP and DRY while improving documentation and type consistency.
Validating refactoring against the project test suite is required because behavior-preserving changes must not alter external functionality. Running tests ensures that improvements to readability, maintainability, and consistency remain safe and do not introduce regressions.
arcasilesgroupRefactor existing code to improve internal structure without changing external behavior.
RaiderIOResolve PHPStan errors with type annotations, PHPDocs, and code improvements.
VoDaiLoczAutomate linting and static analysis of code in CI pipelines.
changgengluValidate PHP/Laravel codebases for SOLID design principle conformance.
