arch-review

To check for circular dependencies, use scripts to scan the `src/` directory and identify import cycles. This validation catches architectural violations automatically before merging code changes.

Enforce UI to Service to Repository layering by using Grep and Glob scripts to check for layer violations. This validates that components adhere to strict architectural boundaries and prevents skipping layers.

Yes, you can analyze code complexity and naming conventions automatically by running Bash scripts. These scripts validate code changes against predefined rules to ensure design quality before merging.

The best way to prevent architectural violations is to automatically validate code changes against predefined rules. Checking for layer violations and circular dependencies using Grep and Glob ensures structural integrity.

Yes, the architectural review works without external dependencies. It relies solely on built-in scripts using Grep, Glob, and Bash to validate design quality and detect layer violations.

You should run an architecture review before merging a significant refactor. This ensures new code adheres to established architectural patterns and does not introduce new violations or circular dependencies.