How does this skill help with commit messages?

It enforces a clear naming convention, using 'Refactor:' prefixes for structural changes so reviewers can immediately identify commits that shouldn't change behavior.

When should I avoid using the Tidy First skill?

Avoid tidying unrelated code 'while you're there' or during urgent bug fixes where the priority is the minimal change necessary to restore service.

What is the Tidy First methodology?

Tidy First is an approach where you perform structural code cleanups (tidying) in separate commits before adding new behavioral logic or features to keep history clean.

Why should I separate structural and behavioral changes?

Separating them makes code reviews easier, reduces the risk of bugs being hidden within refactors, and allows for simpler reverts if a specific change causes an issue.

Is Tidy First compatible with Test-Driven Development (TDD)?

Yes, it perfectly complements the TDD cycle by providing a rigorous framework for the 'Refactor' phase after a test has reached the 'Green' state.

Tidy First Methodology

Name: Tidy First Methodology
Author: kaneshin

bykaneshin

0•

Developer Tools

Enforces the separation of structural code cleanup from behavioral changes to ensure clean, focused commits and maintainable codebases.

The Tidy First skill implements Kent Beck’s 'Tidy First?' philosophy within Claude Code, guiding developers to separate refactoring (structural changes) from new feature development (behavioral changes). By enforcing a workflow where code is tidied before logic is added, it ensures that every commit is atomic, easier to review, and less prone to regressions. This skill is essential for maintaining high-quality standards in collaborative environments and managing technical debt systematically during the development process.

Key Features

01Provides a structured workflow for tidying code immediately before adding new functionality

02Identifies gray area changes to help developers decide when to tidy versus when to build

030 GitHub stars

04Enforces commit discipline with standardized 'Refactor:' prefixes for structural updates

05Validates code integrity by ensuring tests pass before and after structural changes

06Separates structural changes (refactoring) from behavioral changes (features/fixes)

Use Cases

01Standardizing commit history during large-scale refactoring or variable renaming efforts

02Improving code review efficiency by providing focused, single-purpose commits

03Preparing a complex or legacy codebase for a new feature implementation

What are Skills?·How to Install

Install with 🐟 Skill.Fish

npx skillfish add kaneshin/incubator tidy-first

For use in Claude.ai and ChatGPT

Download Skill