module-design-check

Audit Gradle module boundaries and dependency direction for architectural violations.

Updated Jan 4, 2026

Search Tags:#architecture #scope #gradle #code-review #cross-domain #module-design #dependency-direction

Ready to run

npx skills add https://github.com/YeaChan05/Remittance --skill module-design-check

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: module-design-check
Source: https://github.com/YeaChan05/Remittance/tree/main/.codex/skills/module-design-check
Command: npx skills add https://github.com/YeaChan05/Remittance --skill module-design-check

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Audit module boundaries, Gradle dependency direction, and cross-domain exposure for specific modules or changed files. Do not use for behavior review, code-style cleanup, or feature implementation.

Core Features & Use Cases

Identify violations in module structure and dependency direction within a diff or targeted scope.
Verify aggregate assembly scope, API-exposure boundaries, and cross-domain references across modules.
Produce a concise report that lists violations with file paths and broken rule names.

Quick Start

Run the module-design-check on the target module scope to surface structural and dependency violations.

Frequently Asked Questions about module-design-check

High-intent search queries and answers about installing and using this skill.

FAQPage Schema

How do I audit Gradle module boundaries and dependency directions?▼

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.

What is a module boundary check in Gradle architecture?▼

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.

How do I find cross-domain reference violations in 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.

Do I need settings.gradle.kts to check module dependency direction?▼

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.

When should I not use an architecture module design check?▼

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.