Tidy First - Structural Changes Only

Overview

This skill implements Kent Beck's "Tidy First" philosophy. It focuses exclusively on structural improvements that make code easier to work with, without changing any behavior. These changes are committed separately from behavioral changes to maintain clear change history.

When to Use

Use this skill when:

• Code structure is hindering progress
• About to add new behavior but code is messy
• Want to improve code readability before changes
• Need to separate structural from behavioral commits
• Following Tidy First workflow

Philosophy

Tidy First Principle:

Make the change easy, then make the easy change