simplify

Run the test suite first to establish a baseline, then apply behavior-preserving changes like dead code removal, duplicate extraction, and nesting reduction. Run the tests again afterward to confirm nothing broke.

Identify blocks repeated 3 or more times and extract them into shared functions or modules. This Skill targets duplication meeting that threshold and verifies the refactor with the existing test suite.

Avoid it for new feature development, document restructuring, or large multi-target refactoring efforts. Those scenarios need dedicated feature development or full refactoring workflows instead of wrap-up cleanup.

No, the constraints explicitly forbid changing business logic or adding features. Only structural changes like flattening nesting beyond 3 levels are applied, and tests confirm behavior is preserved.

A pre-refactor test run establishes a known-good baseline so any failure afterward is attributable to the changes. The post-refactor run confirms the cleanup preserved behavior, reducing rollback risk.