techdebt

To scan a codebase for tech debt, run a sweep at the repository root to identify duplicates, dead exports, unused dependencies, stale TODOs, and bloated files across multi-language repositories. It returns a structured, fix-oriented report for quick actions.

The best way to detect dead exports and unused dependencies is an end-of-session sweep that flags public exports never imported anywhere, excluding entrypoints, alongside unused dependencies. It groups findings by severity for fast, mechanical fixes.

Yes, you can run a quick health check for file bloat and duplicated code in a multi-language repository. The scan applies across multiple languages, surfaces oversized files and duplicated blocks, and suggests fast, scoped quick fixes.

To preview tech debt findings without modifying code, run the scan in a dry-run mode at the repository root. This surfaces the report of hotspots, including dead code and stale TODOs, so you can review them before applying any changes.

Yes, a lightweight tech debt sweep works across different programming languages in one scan. It is designed to apply across multi-language repositories to identify duplicates, dead exports, and bloated files simultaneously.