Code Rot Cleaner

Find removable code without confusing “not found by a regex” with “safe to delete.” Keep the real project unchanged during discovery and proof. Treat deletion as a claim that must survive static checks, dynamic-reference checks, and relevant project commands.

Enforce the safety boundary

Treat invocation of $code-rot-cleaner as consent to inspect the project and create report artifacts only. It is never consent to delete, edit, rename, uninstall, format, or reorganize project code.

• Default to report-only mode.
• Never alter source, manifests, lockfiles, tests, configuration, generated files, or dependencies during discovery.
• Save generated evidence under outputs/code-rot-cleaner/ unless the user chooses another location.
• Require approval before executing repository-controlled build, test, lint, typecheck, or package-manager commands; those commands can run arbitrary code.
• Run removal experiments only in a disposable copy. Never present that copy as the user's working tree.
• Require a second, explicit approval before changing the real project. Approval must name exact candidate IDs and files.
• Preserve dirty worktrees and unrelated user changes. Never reset, clean, or rewrite history.

Before real cleanup, present and stop at: