techdebt

To find and remove duplicate code, run a static analysis scan that detects copy-paste duplications, similar function bodies, and repeated literals. The tool provides file:line references and concrete fix suggestions for interactive application.

The best way to identify dead code and unused imports before a refactor is to perform a full repository scan. This surfaces unreachable paths, commented-out blocks, and exports that are never imported, producing a prioritized list of findings with file:line references.

You can detect unnecessary abstractions and over-engineered code structures by running a code analysis tool that surfaces indirection adding no value. The scan prioritizes these findings alongside dead code and duplications, offering concrete suggestions to simplify the codebase.

Yes, you can scan only modified files in your current git session for technical debt. The tool applies directly to pending changes to list duplications, dead code, and over-abstractions without requiring a full repository scan.

You verify that removing dead code doesn't introduce regressions through test-based regression verification. After interactively selecting and applying fixes, the process runs tests to ensure the suggested changes do not break existing functionality.

You should run a code analysis scan for technical debt at the end of a coding session, after implementing multiple related features, or before a major refactor. This helps reduce clutter and prevent regressions when the codebase feels overloaded.