refactor

You reduce code complexity by applying structured refactoring rules that extract methods, decompose conditionals, and reduce coupling. This process systematically transforms code smells into lower-complexity, maintainable patterns using vetted transformations.

The safest way to refactor involves using impact-prioritized rules with explicit constraints. By following structured guidance with "when NOT to use" checks and incorrect versus correct examples, you minimize harmful or unnecessary code transformations.

You decompose complex conditionals and simplify readability by applying targeted refactoring rules. These rules provide specific techniques for conditional simplification and naming conventions to standardize code structure and improve clarity.

You should avoid automated refactoring when changes fall under explicit "when NOT to use" constraints defined by specific rules. These safety checks prevent unnecessary refactors that might increase coupling or fail to improve maintainability.

Yes, you can use Clean Code principles to extract methods and classes from existing code. The refactoring process applies these principles alongside Martin Fowler's structured guidance to perform agent-assisted code improvements.