Clutter inventory is handled by this skill in a customer-readable, reusable workflow.
Rollback plan is handled by this skill in a customer-readable, reusable workflow.
What is this?
A messy repository is dangerous because the wrong cleanup can delete the very evidence or source material future work needs. Codebase Hygiene Governor inventories stale routes, duplicate docs, generated output, old drafts, backups, and unclear files, then classifies what is source, artifact, backup, or cleanup candidate. It prepares a reversible cleanup plan before anything important is moved or deleted.

When this helps
- Hygiene inventory
- Cleanup manifest
- Keep/remove rationale
- Rollback notes
- The repository has accumulated old drafts, generated files, duplicate documents, unused routes, or unclear backup folders.
- You want to clean the project, but deleting by instinct could remove source material, evidence, or files another workflow still needs.
- You need a reversible cleanup plan so future AI sessions stop choosing the wrong files.
- It should not delete active work without owner-approved scope and recovery planning.
Cleaner repo -> Less file confusion -> Safer future edits
Asking AI to clean the repo by filename is dangerous because temporary, generated, deprecated, and still-active files can look similar. Codebase Hygiene Governor is stronger because it inventories clutter, classifies candidates, proves references, and prepares reversible cleanup before anything important is removed. The buyer gets a cleaner project without gambling with source knowledge. Boundary: It should not delete active work without owner-approved scope and recovery planning.
Included interface patterns
Reusable hygiene scan intake workflow support.
hygiene-scan-intake.mdReusable cleanup candidate matrix workflow support.
cleanup-candidate-matrix.mdReusable recovery manifest workflow support.
recovery-manifest.md