Tech Debt Auditor

Systematically find and remove duplicated code, dead code, and other forms of technical debt — prioritized by impact, executed with the smallest safe changes possible.

Skill workflow — these skills chain naturally: refactoring-plan (plan the larger structural changes) → techdebt (execute the cleanup) → tdd (lock in behavior with tests before removing debt)

Debt Categories

Technical debt comes in several distinct flavors. Knowing which kind you're dealing with shapes how you approach the fix.