What it does
Technical Debt Auditor scans a codebase and produces a quantified technical debt report with a prioritized remediation plan. It analyzes dead code, TODO, FIXME and HACK markers, dependency staleness, complexity hotspots, code duplication signals, test coverage gaps, unused exports and outdated patterns.
It suits requests for a code quality audit or health check, such as asking where to focus refactoring, finding code smells, or prioritizing cleanup work. The description also covers legacy cleanup, code rot, and assessing a project's overall health before a major effort, and it applies even when the user does not mention technical debt directly.
As a skill, it is triggered by requests phrased in these ways. The source gives no further setup steps.
Safety
Our team has not reviewed this resource. Only automated rules checked it; resources with high-risk signals are not published. These are signals, not a guarantee that installing it is safe. Try it in a sandbox project first.
- Runs code or changes an assistant's behaviour
Sources
- AI Templates (aitmpl) first seen 13 Nov 2026 · last seen 18 Nov 2026 · its page on the source · figures reported by the source: aitmpl downloads 6
technical-debt-auditor
Scans a codebase and produces a quantified technical debt report with a prioritized remediation plan. Analyzes dead code, TODO/FIXME/HACK markers, dependency staleness, complexity hotspots, code duplication signals, test coverage gaps, unused exports, and outdated patterns. Use this skill when the user asks to audit their codebase for tech debt, wants a health check of their code quality, says things like "where should I focus refactoring", "find code smells", "audit my codebase", "what technical debt do we have", "prioritize cleanup work", or asks about code quality metrics. Also trigger when
As shown on www.aitmpl.com when we last read it