code-cleanup

To remove dead code and unused imports across multiple languages, apply cross-language cleanup rules that delete redundant code paths without reformatting your files. This skill handles Dart, Bash, Python, Java, Kotlin, Swift, and TypeScript projects to improve maintainability.

The best way to prune empty directories and clean up code without changing formatting is to use a tool that enforces cleanup actions independently of code formatters. This ensures your repository stays clean while preserving your existing styling and layout conventions.

Yes, this code cleanup approach works with both Swift and Kotlin projects, alongside Dart, Bash, Python, Java, and TypeScript/JavaScript. It applies analyzer fixes and lint checks to remove dead code and unused imports across all these supported environments.

Static analysis and linters integrate with dead code removal by identifying unused imports and redundant code paths, then applying analyzer fixes to reach a healthier codebase. This skill relies on existing analyzers to enforce cleanup actions without applying code formatting.

Yes, you can use this to clean up unused imports in TypeScript and JavaScript repositories. It deletes unused code paths and redundant imports across your project while preserving behavior and ensuring analyzer compliance without reformatting your code.