Detect codebase bloat through progressive analysis: dead code, duplication, complexity, documentation bloat. Triggers:…
Detect codebase bloat through progressive analysis: dead code, duplication, complexity, documentation bloat. Triggers: bloat detection, dead code, code cleanup, duplication, technical debt, unused code Use when: context usage high, quarterly maintenance, pre-release cleanup, before refactoring DO NOT use when: active feature development, time-sensitive bugs, codebase < 1000 lines
athola
cli
free
Others in the same category, ranked by how often they are opened.
