Tech Debt Audit
Scan, catalog, and evaluate technical debt across a repository to produce an actionable, prioritized remediation plan. Evaluates architectural decay, missing test coverage, deprecated dependencies, and dead configuration layers without mutating source files.
Technical Debt Classification Matrix
| Dimension | Indicators | Severity Score (1-10) |
|---|---|---|
| Architectural | Circular dependencies, leaky abstractions, monorepo boundary violations | High (7-10) |
| Code Quality | Complex God-classes, high cyclomatic complexity, copy-paste duplication | Medium (4-6) |
| Testing | Untested critical paths, flakiness, missing regression mocks | High (7-9) |
| Dependencies | Outdated major packages, unmaintained libraries, security advisories | Medium-High (5-8) |
| Documentation & Typings | Inaccurate docstrings, implicit any types, missing interface contracts |
Low-Medium (2-5) |
Audit Steps
- Static Analysis & Metrics Collection:
- Inspect repository structure and file distribution.
- Run type-checkers (
tsc --noEmit,mypy, orcargo check). - Identify TODO, FIXME, HACK, and DEPRECATED markers.
- Prioritization Scoring:
- Calculate Effort vs. Impact ratio for each debt item.
- Generate Debt Scorecard:
- Save report to
${EVIDENCE_DIR:-.evidence/tech-debt}/debt-scorecard.md.
- Save report to