cm-clean-codelisted

# Clean Code — Code Hygiene Gate ## TL;DR - **Use after** a feature lands, before PR review - **Detects**: dead code, duplicates, naming smells, dependency drift - **Powered by** TRIZ contradictions and Boy Scout rule - **Next**: cm-code-review > **Code that works is not enough. Code must be CLEAN.** > Inspired by Clean Code (Robert C. Martin) + Refactoring (Martin Fowler) + TRIZ. ## When to Use **ALWAYS when:** - After completing a feature (mandatory hygiene pass before PR) - After `cm-reactor` migration (cleanup dead code from migration) - Before code review (`cm-code-review`) — clean FIRST, review AFTER - During technical debt sprints - When code smells are detected (see Detection section) - After AI-generated code sessions (AI tends to leave mess) - When file grows beyond 300 lines **Run automatically after:** - `cm-execution` completes a task batch - `cm-reactor` Phase 5 (post-migration cleanup) - `cm-tdd` Refactor phase (Red → Green → **Refactor**) **Skip when:** - Quick hotfix (patch first, clean later — but schedule the cleanup!) - Prototype/spike code (will be thrown away) ## TRIZ Principles Applied | # | Principle | How Applied | |---|-----------|-------------| | **#1** | Segmentation | Break large files/functions into focused units | | **#10** | Prior Action | Clean BEFORE it rots — don't wait for tech debt sprint | | **#6** | Universality | One function should serve one purpose (SRP) | | **#27** | Cheap Short-living | Quick small cleanups > expensive large