codebase-audit

To audit an unfamiliar codebase before architecture work, run this skill against the target repository to map project scope, assess 20 audit areas, and generate AUDIT-FINDINGS.md and QUESTIONS.md. This structured approach identifies risks and knowledge gaps before implementation.

Performing technical due diligence on a monorepo involves mapping entry points, dependencies, and architecture to document risks. This skill applies a repeatable methodology to generate AUDIT-FINDINGS.md and QUESTIONS.md, reducing knowledge gaps across mixed-language projects.

Yes, you can use this codebase audit for developer onboarding into a mixed-language project. It maps the repository scope and architecture, producing AUDIT-FINDINGS.md and QUESTIONS.md to guide new developers through risks, technical decisions, and necessary clarifications.

The codebase audit process works by enforcing deliverables through a structured assessment of 20 audit areas. It maps the repository structure and generates AUDIT-FINDINGS.md and QUESTIONS.md, systematically documenting risks, decisions, and required clarifications before implementation.

No dependencies are required to map repository scope and assess architecture risks. The skill operates independently to evaluate the codebase, identify structural risks, and produce AUDIT-FINDINGS.md and QUESTIONS.md for architectural planning and pre-implementation reviews.

From a pre-implementation codebase review, you should expect AUDIT-FINDINGS.md and QUESTIONS.md as deliverables. These documents map the repository, outline 20 assessed audit areas, and capture risks, decisions, and clarifications needed for safe architectural planning.