prune-unused-code

Unused code removal deletes unreferenced imports, dead functions, and commented-out blocks automatically. Run this skill after `detect-unused-code` identifies unused code targets to safely prune them while preserving active code and running tests to confirm no regressions occur.

Yes. The skill runs all tests before and after pruning, with automatic rollback on failure. It performs line-level deletions and import edits based on detection reports, preserves used code, backs up changes, and generates deletion logs for full traceability.

The skill automatically rolls back changes if any test fails after pruning. This safety check ensures no regressions are introduced and your codebase remains stable throughout the cleanup process.

Run `detect-unused-code` first to generate a tech debt report identifying unused imports, dead functions, and commented-out blocks. The skill then uses this report to target and remove the unused code safely.

The skill requires tests to run before and after pruning to validate no regressions occur. Codebases with minimal or no test coverage cannot guarantee safe removal, so establishing tests first is a prerequisite.

Dead code removal addresses technical debt by eliminating commented-out blocks, unused imports, and orphaned functions identified in detection reports. Automating cleanup prevents gradual codebase bloat and keeps repositories lean.