analyze

To audit technical debt and quality issues, run a parallel codebase scan that checks code quality, conventions, security, and testing signals to produce a consolidated health report with a prioritized scorecard.

A codebase health report aggregates automated audit findings into a scorecard, highlighting critical issues, technical debt, and improvement opportunities to guide architectural refinements and maintainability.

Yes, you can apply a specific scope or focus area when initiating the codebase audit, which narrows the parallel assessment of code quality, conventions, security, and testing to that targeted section.

Yes, the audit runs dedicated convention-auditor and security-auditor agents alongside code-quality and test auditors to identify convention violations, security vulnerabilities, and testing gaps.

The best way to identify technical debt before a release is to run an automated health snapshot that scans for quality issues and convention deviations, delivering prioritized recommendations for refactoring.

You can prioritize refactoring tasks by using the consolidated health scorecard from the audit, which ranks critical issues, technical debt, and improvement opportunities aligned with development lifecycle requirements.