code-cleaner

You can remove dead code and unused exports from changed TypeScript files by analyzing git diffs to identify and delete unused functions, types, and interfaces. This Skill targets modified files to eliminate unnecessary code, ensuring only actively used code remains for better maintainability.

Cleaning up console logs and unused functions after AI code generation is best handled by automating code hygiene through git diff analysis. This identifies and removes leftover debugging statements and dead code, ensuring only essential, actively used code remains in your project.

This dead code removal tool analyzes just the changed files by evaluating git diffs, rather than scanning the entire repository. It focuses on modifications in your TypeScript and JavaScript files to selectively eliminate unused exports, functions, and console logs.

Adaptive parallelization handles dead code elimination by sequentially analyzing a small number of JavaScript files, while processing larger sets through parallel analysis followed by sequential modification. This optimizes the cleanup of unused code across multiple changed files efficiently.

Yes, you can remove unused types and interfaces from your JavaScript project using this tool. It identifies and eliminates dead exports, unused functions, types, and leftover console logs by analyzing the git diff of your changed files.

You should not use automated refactoring to remove unused code when your files have not been tracked by git or lack recent diffs, as this tool relies on git diff analysis to identify changes. It is specifically designed to clean up modified TypeScript and JavaScript files.