dead-code-cleanup

Dead code cleanup scans multi-language codebases to identify unused functions, variables, imports, and types, verifying no direct, indirect, dynamic, or runtime references exist before reporting exact file paths and line numbers. It optionally generates safe patches for removal.

Removing dead code after AI-generated changes requires scanning for unused functions, variables, imports, and types while verifying no dynamic or runtime references exist. This cleanup process reports precise file locations and can generate safe patches to prune codebase bloat.

Yes, dead code detection applies to multi-language codebases and verifies direct, indirect, dynamic, and runtime references before marking any item as dead. It excludes items with external usage or safety concerns to ensure accurate unused code identification across different languages.

Safe unused code removal requires verifying no direct, indirect, dynamic, or runtime references exist before marking items as dead. The tool excludes items with external usage or safety concerns and reports confirmed dead code with precise file paths and line numbers for manual or patched review.

Yes, you can optionally generate safe patches when removing unused imports and types. The tool identifies dead code candidates, verifies no references exist across direct, indirect, dynamic, or runtime usage, and proposes patches with precise file paths and line numbers for maintainability.