refactor-clean

To safely remove dead code, this Skill identifies unused code and proposes deletions categorized as SAFE, specifically avoiding critical areas like entry points. It verifies codebase integrity by running the full test suite before and after each deletion.

The best way to find unused code after a refactor is to use analysis tools like knip, depcheck, and ts-prune. This Skill utilizes these dependencies to accurately detect dead code, duplicates, and unused exports for cleanup.

Yes, dead code removal works with TypeScript projects by utilizing ts-prune to detect unused exports. The Skill integrates this analysis to safely prune unreferenced code, ensuring a cleaner and more efficient project.

Test verification ensures codebase integrity by running the full test suite before and after each proposed deletion. This mechanism guarantees that removing identified dead code and duplicates does not break existing software development workflows.

You cannot automatically delete code from critical areas like entry points, as the Skill only suggests deletions categorized as SAFE. It targets utilities and unreferenced code while running test suites to prevent breaking core application functionality.

You should remove dead code and duplicates to reduce increased complexity, maintenance overhead, and larger bundle sizes. Cleaning up unused exports ensures a cleaner, more efficient project structure and optimizes overall code hygiene.