tech-debt-audit

A codebase architecture audit evaluates structural weaknesses and technical debt across nine dimensions, surfacing issues like type contract drift and test debt with specific file and line citations for targeted remediation.

Documenting code quality issues is best achieved by generating a persistent TECH_DEBT_AUDIT.md file in the repository root, providing an executive summary, quick wins, and scoped remediation guidance that can be committed and tracked over time.

Yes, static analysis can be performed on an entire repository to identify debt and provide scoped remediation guidance instead of requiring full rewrites, ensuring you can address issues like error handling and security hygiene incrementally.

A code audit handles documentation drift and configuration debt by systematically evaluating these specific dimensions during the audit phase, grounding every concrete finding with path and line references in the final deliverable.

The tech debt audit workflow supports large repositories by utilizing subagents to scale the analysis, following a repeatable three-phase process of orientation, auditing, and deliverable generation to manage the workload effectively.

You should avoid an automated codebase audit if your project requires understanding complex runtime behavior rather than static structural debt, as the audit focuses on static analysis, architectural decay, and persistent artifact generation.