dead-code-cleanup

To remove dead code, analyze your repository to detect unused exports, deprecated functions, and orphaned files. You can run a dry-run first to report findings, then apply automated deletions while enforcing preservation rules for public APIs and tests.

Yes, detecting unused exports and orphaned files is safe when using a dry-run mode. This reports dead code without deleting it, allowing you to verify integrity and ensure your build passes before applying any actual changes.

The best way to clean up deprecated code is to scan for TODO and FIXME markers, identify unreferenced functions, and remove them in batches. You must run your standard build and tests after each batch to maintain project integrity.

Yes, dead code cleanup enforces preservation rules to protect public APIs, tests, and critical build assets. This ensures that automated deletions of unused code never remove essential components required for your project to function.

You can automate unused code removal by running an auto-delete command against your repository path. This automatically prunes dead code while respecting preservation rules, though you must verify that the project builds and passes tests afterward.