What problem does it solve? When you face messy code and need to make a behavior change, it is unclear whether to clean up first, after, later, or never — and mixing structure changes with behavior changes in one commit makes reviews, reverts, and debugging harder. This Skill provides a decision framework and a catalog of small, safe structural changes to resolve that. ## Core Features & Use Cases - Tidyings Catalog: Fifteen small, reversible structure changes such as guard clauses, explaining variables, extract helper, dead code deletion, and reading order. - Four Timings Framework: Decide for each tidying whether to tidy first, after, later, or never, based on risk, scope, and economics. - Economic Design Reasoning: Frame design decisions as investments using coupling, cohesion, optionality, and discount rate. - Use Case: You are about to fix a bug in a tangled method. The Skill helps you extract a helper and add guard clauses as separate tidy: commits first, then make the behavior change with green tests on both sides. ## Quick Start Ask Claude to review this messy method and suggest which tidyings to apply before making my behavior change.
