Codebase Audit
Audit an existing codebase or system and produce an evidence-backed findings register and prioritized remediation roadmap. Covers scoping the audit questions, a read-only orientation, eight dimensions (architecture, maintainability, reliability, security, performance, test coverage, operability, delivery), change-frequency by complexity hotspots, test-gap mapping to critical paths, findings with evidence and confidence, severity times likelihood times exposure scoring, and now/next/later sequencing. Use when someone asks to audit a codebase, assess technical debt, review the health of an inherited or acquired system, find reliability or security gaps, judge whether to rewrite or refactor, or prepare due diligence on a code base. Do not use for dependency version and licence health alone (use dependency-health), for planning a data or platform move (use migration-plan), for designing the target system (use technical-architecture), or for reviewing a single change (use gitnexus-review).