How does Tidy-Up 150 prevent scope creep?

It enforces a strict 'objective-only' rule, meaning it only touches provable defects like syntax errors or unused code, and limits total time to 5% of the original task duration.

Is the code cleanup reversible?

Yes, every fix proposed by Tidy-Up 150 is designed to be easily reversible and the protocol ensures that tests pass before and after execution.

What qualifies as a 'tidy-up' item?

Only objective defects like syntax errors, dead code, poor naming, unused imports, and obvious typos qualify. Complex refactors or architectural changes are strictly forbidden.

Can I use this after every small code change?

No, it is designed to be used specifically after key milestones, such as completing a feature or a major bug fix, to avoid disrupting active development flow.

Tidy-Up 150

Name: Tidy-Up 150
Author: MykhailoDmytriakha

byMykhailoDmytriakha

Developer Tools

Performs rapid, safe, and objective code cleanup after reaching development milestones to eliminate minor technical debt.

About

Tidy-Up 150 is a high-efficiency protocol for Claude Code designed to handle essential housekeeping tasks immediately following the completion of a project milestone. It scans for objective defects such as syntax errors, dead code, unused imports, and naming inconsistencies while adhering to a strict time budget—never exceeding 5% of the main task duration. By focusing only on reversible, low-risk fixes that take less than 30 seconds each, this skill ensures your codebase remains clean and professional without the risks of architectural scope creep or unexpected regressions.

Key Features

Milestone-based cleanup triggers to maintain development momentum
Objective defect scanning for syntax, dead code, and naming issues
Automated reporting of cleanup impact and time spent
Strict time-boxing to 5% of main task duration for efficiency
0 GitHub stars
Safety-first verification requiring user approval for all changes

Use Cases

Removing dead code paths and unreachable logic after a major refactoring session
Fixing typos and formatting inconsistencies before pushing code for review
Cleaning up unused imports and temporary variables after implementing a new feature

About

Key Features

Milestone-based cleanup triggers to maintain development momentum
Objective defect scanning for syntax, dead code, and naming issues
Automated reporting of cleanup impact and time spent
Strict time-boxing to 5% of main task duration for efficiency
0 GitHub stars
Safety-first verification requiring user approval for all changes

Use Cases

Removing dead code paths and unreachable logic after a major refactoring session
Fixing typos and formatting inconsistencies before pushing code for review
Cleaning up unused imports and temporary variables after implementing a new feature