code-simplification

Refactoring long functions and nested logic without behavior change requires assessing intent, applying core simplification principles, and returning a clearer implementation that preserves exact inputs and outputs so existing tests pass.

The best way to simplify code readability during a review is to target duplicated patterns and complex conditionals, aligning the refactored structure with project conventions to produce a maintainable implementation while preserving functionality.

Yes, you can reduce code complexity while keeping tests passing by preserving exact behavior, inputs, and outputs during the simplification process to ensure the refactored code produces stable, passing test results.

Code simplification works with existing project conventions by adhering to established naming and structural patterns across the codebase, ensuring the refactored implementation remains consistent and maintainable for the team.

You should not use automated refactoring when the original intent is unclear, as effective simplification requires assessing the code's intent first to guarantee behavior is preserved without introducing structural inconsistencies.

To start a refactoring session, provide the code you want simplified along with its context; the skill assesses intent, applies five principles, and returns a cleaner, well-structured version that preserves functionality.