Technical Debt Auditor

A Technical Debt Auditor helps engineering teams understand exactly where their codebase is accumulating risk, complexity, and hidden costs. Instead of vague complaints about 'messy code,' this assistant systematically reviews source files, architecture notes, commit history patterns, and bug reports to build a structured inventory of technical debt items. Each item is categorized by type, such as outdated dependencies, missing tests, duplicated logic, tangled modules, or poorly documented components, and rated by severity and likely business impact. The process works through guided conversation: you describe your codebase, share relevant snippets, architecture diagrams, or pain points, and the assistant asks targeted follow-up questions to narrow down root causes rather than surface symptoms. It then organizes findings into a readable audit report that engineering managers, architects, and even non-technical stakeholders can understand, translating dense technical issues into plain-language risk statements. Expect outputs like prioritized debt registers, dependency risk maps, and concise executive summaries that explain why certain shortcuts are costing the team time, money, or reliability. This is especially useful before a major refactor, after inheriting a legacy system, during due diligence for an acquisition, or when onboarding new senior engineers who need a fast, accurate picture of the codebase's health. Startups preparing for scale, agencies handing off projects, and platform teams justifying refactor budgets to leadership all benefit from a clear, evidence-based audit rather than anecdotal complaints. The assistant does not write production code changes itself; instead it focuses on diagnosis, documentation, and communication, helping you build a shared understanding across the team of what debt exists, how it accumulated, and which items deserve attention first. Results typically include a categorized debt inventory, a severity-ranked list, suggested metrics to track over time, and talking points for conveying urgency to leadership without resorting to fear-based language. Teams that use this role regularly report fewer surprise outages, more accurate sprint estimates, and stronger buy-in for dedicated refactor time because the debt is finally visible, quantified, and explainable rather than an abstract sense of dread hanging over the codebase.