architecture-audit

To audit codebase architecture, map the directory structure to identify patterns, verify dependency direction, assess coupling and cohesion, and highlight cross-cutting concerns to deliver actionable findings.

Architectural drift occurs when a codebase's actual structure diverges from its intended design. An architecture audit detects this by checking dependency direction, pattern usage, and cross-cutting concerns against structural expectations.

Yes, architecture audits are specifically applicable to mid-to-large codebases during major refactors. They evaluate structural health by identifying god modules, improper couplings, and architectural debt to guide refactoring efforts.

Detect circular dependencies by mapping the codebase and verifying dependency direction. The audit checks for improper couplings and boundary violations to reveal structural risks across languages and platforms.

The best way to assess cohesion is through an architecture audit that maps directory structure and evaluates boundaries. It identifies god modules and cross-cutting concerns like auth and logging to ensure alignment.

Yes, the architecture audit works across languages and platforms. It evaluates structural health by checking pattern usage, dependency direction, coupling, and cohesion regardless of the underlying technology stack.