module-design-check

Audit Gradle module boundaries by analyzing settings.gradle.kts and build files to identify dependency direction violations. This process outputs a list of structural violations with specific file paths and broken rule names.

A module boundary check verifies aggregate assembly scope, API-internal exposure, and cross-domain references across modules. It enforces architectural constraints by detecting dependency direction violations within a targeted scope or changed files.

Find cross-domain reference violations by running a module boundary audit on changed files. The audit checks API-exposure boundaries and outputs a concise report listing violations with file paths and broken rule names.

Yes, you need settings.gradle.kts and relevant build files to check module dependency direction. These files provide the project structure and configuration required to identify architectural constraint violations.

You should not use an architecture module design check for behavior review, code-style cleanup, or feature implementation. It is designed strictly to enforce structural constraints and dependency direction within Gradle modules.