What problem does it solve? Working code often ends up harder to read than it needs to be: deep nesting, long functions, nested ternaries, and duplicated logic slow down reviews and future changes. This Skill guides behavior-preserving refactoring so code becomes easier to understand without risking regressions. ## Core Features & Use Cases - Behavior-Preserving Refactoring: Every simplification must keep inputs, outputs, side effects, and error behavior identical, with explicit verification steps. - Five Guiding Principles: Preserve behavior, follow project conventions, prefer clarity over cleverness, avoid over-simplification, and scope changes to what recently changed. - Structured Four-Step Process: Understand the code first, identify simplification signals (deep nesting, dead code, misleading names), apply changes incrementally, then verify the final diff. - Use Case: After a feature passes its tests but the implementation feels heavy, run this Skill to flatten nested conditionals, rename unclear variables, and remove dead code while keeping the test suite green. ## Quick Start Ask the agent to simplify the recently modified function in the current file without changing its behavior, following the simplify skill.
