workflow-codebase-audit

A codebase audit performs a time-boxed, multi-axis sweep across security, reliability, performance, tooling, and testing to uncover technical debt and security issues. It produces evidence-backed findings using a strict reasoning schema to ensure accuracy.

To perform a pre-refactor tech-debt sweep on an unfamiliar codebase, activate a cold-start audit. It assesses the codebase across multiple domains and returns prioritized findings ranked by a severity-confidence-effort formula to guide your refactoring.

Yes, you can use an automated codebase audit for post-acquisition due-diligence reviews. It quickly assesses unfamiliar codebases to deliver take-home readiness, revealing risk, quality, and architectural issues without spending weeks onboarding.

The best way to analyze inherited-service reliability and security risks is a cold-start audit with optional deep mode fan-out. This performs deeper root-cause debugging for reliability issues and threat/CVE analysis for top security findings.

Yes, a multi-domain codebase audit enforces structured reasoning by applying an 11-field schema per finding. It requires root cause, reasoning chain, and counter-evidence considered, dropping incomplete findings to maintain complete reasoning integrity.

Codebase audit findings are ranked using a severity-confidence-effort formula. This scoring mechanism evaluates the impact, certainty, and required remediation work to produce a prioritized, multi-domain view of your codebase.