onboard-codebase

To understand an unfamiliar codebase, generate an architecture overview and dependency analysis. This maps module structures, identifies entry points, and audits documentation to reveal unusual patterns and historical project changes.

Mapping dependencies between modules requires analyzing structural connections and layer relationships. This process highlights how different parts of the codebase interact and identifies unusual patterns within the architecture.

Analyzing project history involves reviewing past changes and issues using memory history. This provides historical insights into how the codebase evolved and highlights previous architectural decisions and dependency shifts.

Codebase orientation includes a document quality audit that validates the completeness of CLAUDE.md. While orientation can still map architecture, lacking a complete CLAUDE.md file means missing validated context for the overall structure.

Yes, codebase orientation for large projects uses parallel tree-mapping and symbol analysis. This combination efficiently processes complex project structures to provide a high-level summary and dependency mapping.

Dependency mapping might miss unusual patterns if the project structure lacks clear module separation or if historical changes are not analyzed. Accurate detection requires combining tree-mapping, symbol analysis, and document audits.