tech-debt-audit

To generate a tech debt audit, run the audit command in your repository root. It executes a three-phase protocol that evaluates architecture, tests, and security, then writes a citable, actionable report directly to TECH_DEBT_AUDIT.md.

A file-cited architecture review is a codebase health assessment that grounds every concrete technical debt finding in specific file:line citations. This replaces shallow, generic code reviews with evidence-based architectural decay analysis.

Yes, you can run a whole-repo quality engineering assessment on growing codebases. The audit evaluates consistency rot, type debt, dependency configurations, and documentation drift to provide a repeatable health check.

The best way to prioritize refactoring is to generate a ranked deliverable with an executive summary and quick wins. The audit enforces a non-empty section for things that look bad but are actually fine, preventing checklist-style rewrites.

No, the tech debt audit explicitly enforces no rewrite-style recommendations. It focuses on actionable, prioritized improvements and quick wins rather than suggesting complete system rewrites for inherited repositories.

A codebase analysis for technical debt covers architecture, consistency, types, tests, dependencies, performance, error observability, security hygiene, and documentation drift. It requires file:line citations for every concrete issue found.