review-architecture

You can validate code changes by running an automated compliance check that verifies module imports, enforces layer separation, and detects unidirectional dependency violations against your architectural blueprints before merging.

Enforcing modularity and dependency rules requires checking code diffs against repository conventions and design documents like architecture.md, ensuring new features respect defined module boundaries and specified design patterns.

Architectural compliance checking for code refactoring is the process of verifying that modified code still adheres to established architectural principles, directory structures, and design patterns to prevent technical debt and maintain system integrity.

Yes, you can use design documents like architecture.md and design.md as references to automatically check if code implementations respect defined layer separation, dependency rules, and specified module boundaries during development.

Yes, architectural review works for checking unidirectional dependencies by validating new feature implementations against project architecture guidelines, confirming that module imports are correctly structured and comply with defined rules.