unused-code-refactor-suggester

To find unused functions and dead code, you can scan individual source files or directories to pinpoint file-scoped definitions without internal references. This generates a refactoring report recommending deletion or preservation with risk summaries for each identified item.

File-scoped unused code detection scans individual source files to pinpoint functions, classes, and top-level definitions that lack internal references within that same file. It then flags these unreferenced definitions as dead code for potential cleanup.

To clean up dead code after a large refactor, run a file-scoped scan on your target directories to generate a refactoring report. This report identifies unreferenced functions and classes, recommending whether to delete or keep them based on concise risk assessments.

Unused code detection operates at the file-scoped level, scanning individual source files or specified directories to find definitions without internal references. It does not track cross-file dependencies, so it focuses strictly on dead code contained within its own file.

Yes, you can get a risk assessment before removing dead code. The generated refactoring report provides clear recommendations to either delete or keep identified unused functions and classes, accompanied by concise reasons and risk summaries for safe removal.

The best way to remove unused classes and top-level definitions is to scan the target source files for unreferenced items and generate a refactoring report. This provides clear deletion or preservation recommendations with risk summaries to guide safe code cleanup.