remove-deadcode

To safely remove unused TypeScript code, the Skill uses Language Server Protocol (LSP) reference verification to ensure only unreferenced imports, functions, and files are deleted. It executes project-wide automated refactoring tasks to eliminate dead code without causing runtime errors.

LSP reference verification prevents runtime errors by checking all references across the project before deleting any code. It ensures that only truly orphaned files and unused imports are purged, maintaining strict type safety throughout the atomic deletion process.

Yes, you can use parallel agents to speed up large-scale TypeScript dead code cleanup. The Skill orchestrates multiple deep agents simultaneously to perform batch removals, significantly accelerating refactoring across large codebases while maintaining conflict-free execution.

Yes, you need Git integration to automate TypeScript dead code removal. Git is required to ensure type-safe deletions are committed atomically, enabling conflict-free parallel execution and safe rollback if any refactoring task produces unexpected results.

The best way to reduce technical debt by removing unused imports is running an automated, project-wide scan that identifies clutter and verifies references. This process strips unused code while preserving strict type safety through atomic git commits.

A key limitation is that automated dead code removal relies entirely on LSP reference verification, meaning dynamically referenced code might not be detected as used. Additionally, it strictly requires a TypeScript compiler and Git integration to function properly.