refactor

The Refactor skill is designed for developers who need to improve existing codebases through systematic, incremental changes. It focuses on cleaning up technical debt, enhancing readability, and optimizing code structure without impacting functional requirements or external system behavior. This tool is ideal for scenarios where functions have become too large, classes have grown into 'god objects,' or code smells are hindering feature development. By automating the identification and remediation of common anti-patterns, it empowers developers to maintain high standards of code quality throughout the software lifecycle. Users provide a specific module, function, or class, and the agent acts to decompose logic, apply appropriate design patterns, and ensure type safety.

• Extracts complex logic into focused, reusable functions and methods.

• Identifies and eliminates code smells such as Feature Envy, Long Parameter Lists, and Magic Numbers/Strings.

• Facilitates the transition from monolithic classes to single-responsibility modules.

• Automatically restructures code to improve readability and testability.

• Encapsulates domain concepts into proper types or classes to move away from primitive obsession.

• Ensures adherence to clean coding principles and design patterns.

• Always ensure unit tests are in place before triggering refactoring; this skill assumes tests exist to verify that behavior is preserved.

• Best suited for iterative, gradual improvements rather than complete system rewrites.

• Avoid using this skill on critical production code that lacks existing test coverage.

• Use the 'small steps' approach by committing changes frequently to version control between operations.

• Input expected is usually a block of code or a file segment; output is a refactored version that preserves the original logic while simplifying the structure.

• When a refactor is proposed, verify the logic against original expectations to ensure no side effects are introduced.