tidy-firstlisted

# Tidy First Follow Kent Beck's "Tidy First" approach by strictly separating structural changes from behavioral changes in all development work. ## Source This skill is adapted from the community skill **`snrsw-dotfiles-tidy-first`** on the LobeHub Skills Marketplace. - Original skill page: <https://lobehub.com/skills/snrsw-dotfiles-tidy-first?activeTab=skill> - Raw SKILL.md: <https://lobehub.com/skills/snrsw-dotfiles-tidy-first/skill.md> - Upstream author: [@snrsw](https://github.com/snrsw) — repo: [snrsw/dotfiles](https://github.com/snrsw/dotfiles) - Upstream version referenced: 1.0.1 The instructional content below is the original skill's guidance, lightly reformatted for this dotfiles repo. Marketplace install/registration steps from the upstream page are intentionally omitted — this skill ships directly via `shared/skills/` and is synced to each tool by `scripts/sync-skills.sh`. ## Core Principle Separate all changes into two distinct types: 1. **Structural changes** — rearranging code without changing behavior: - Renaming variables, functions, classes - Extracting methods or functions - Moving code to different files or modules - Reorganizing code structure - Improving code organization 2. **Behavioral changes** — adding or modifying actual functionality: - Adding new features - Fixing bugs - Changing business logic - Modifying functionality ## Golden Rules ### Never mix change types - Never mix structural and behavioral changes in