refactor-audit

To audit technical debt and generate a refactoring plan, specify a codebase scope for analysis. The audit evaluates dead code, complexity, duplication, type safety, and security, then outputs a tiered refactoring plan with actionable file-level changes.

Prioritizing refactoring tasks to improve maintainability is done by analyzing static analysis results and git history. This process identifies technical debt categories like complexity and architectural flaws, generating a prioritized refactoring plan based on actual code health.

Yes, you can generate refactoring subtasks for AI execution from a code audit. The audit produces a prioritized refactoring plan at user-defined detail levels, including high-level subtasks specifically designed for AI execution loops.

Yes, the technical debt audit analyzes both test coverage and dependency health. It systematically evaluates specified codebase scopes across multiple categories including dependency issues, test coverage gaps, type safety, and security smells to inform findings.

You should run a code audit to manage technical debt quarterly. Running this audit proactively ensures the codebase remains healthy, reduces future development friction, and maintains overall maintainability as the project evolves.

A static analysis audit identifies code quality issues across categories including dead code, complexity, duplication, dependency health, type safety gaps, test coverage, architectural flaws, security smells, and readability problems to generate actionable refactoring plans.