Apply small, behavior-preserving structural tidies in separate commits.
npx skills add https://github.com/shishi/dotfiles --skill tidying
Please help me install this Agent Skill. Skill: tidying Source: https://github.com/shishi/dotfiles/tree/main/claude/skills/tidying Command: npx skills add https://github.com/shishi/dotfiles --skill tidying
This skill helps developers apply Kent Beck's Tidy First philosophy to make small, safe structural changes that improve code without changing behavior. Tidying is a separate activity from feature work and is often performed before or after implementing features or during code reviews to keep code clean.
Identify a small, non-behavior-changing tidying opportunity in the target module. Perform the tidy as a separate commit labeled tidy:first before any behavioral changes. If the change reveals a better structure, continue with subsequent tidies following the same discipline.
High-intent search queries and answers about installing and using this skill.
Behavior-preserving refactoring applies tiny structural code changes that improve readability without altering functionality. It works by isolating each structural tidy into a separate commit, ensuring the software's existing behavior remains completely unchanged throughout the process.
To clean up messy code safely during a review, identify small structural issues and perform tiny tidies as separate commits. Follow a tidy-first or tidy-after workflow, keeping each change under fifteen minutes to guarantee no behavioral shifts occur.
Yes, the tidy-first workflow applies across frontend, backend, CLI, and library contexts. It is designed to reduce technical debt in any codebase by guiding developers to make small, safe structural improvements without changing behavior.
The best way to structure commits when tidying code is to isolate every small structural change into its own commit, labeled tidy:first. This separates structural cleanup from feature work, keeping changes reviewable and guaranteeing behavior remains unchanged.
A code tidy should take less than fifteen minutes. Keeping structural changes small ensures they remain safe and behavior-preserving, allowing developers to incrementally reduce technical debt without risking large functional regressions.
atusyApply Tidy First structural refinements to codebases without altering behavior.
vanducngSimplify nested conditionals and long functions without changing behavior.
act70255Automate code reviews with static analysis and AI vulnerability detection.
pproencaGuide architectural refactoring of React applications with structured rules.
