architecture-review

To identify architectural debt, audit your codebase against existing ADRs and the current module graph to surface drift and unresolved decisions. This maps modules, dependencies, and layering to generate a prioritized refactor backlog.

Auditing software architecture for dependency violations involves mapping the current module graph and public surfaces against documented layering rules. This generates a structured findings report with actionable refactor guidance to correct architectural drift.

Yes, existing Architecture Decision Records are required in the docs/adr/ directory. The architecture review reads these prior decisions alongside CLAUDE.md context to ensure proposed refactoring changes align with established team decisions.

The best way to generate a refactoring backlog from a dependency graph is to audit the whole repository or a chosen scope against ADRs. This produces a prioritized, structured findings report of refactor proposals directly consumable by refactoring tools.

Yes, you can target a specific chosen scope rather than the whole repository for an architecture health check. The scope-aware assessment maps the targeted modules and dependencies to generate localized refactor proposals.

Architectural drift accumulates when codebases evolve without resolving ADRs, leading to wasted context. It is surfaced by auditing the codebase, mapping dependencies and layering, and generating a structured findings report with actionable refactor guidance.