Agent skill · data analytics · aiskillstore
ddd-check-full
Full-project DDD compliance audit — scans ALL Java files against every DDD layer rule. Use for architecture reviews, onboarding, and pre-release checks.
Why this skill is useful
Adds a comprehensive executable script for auditing DDD compliance across all Java files, which the AI cannot generate from knowledge alone.
What it needs
Requires bash installed locally. About 3k tokens when loaded. Last updated 2026-08-07. 405 stars on the source repository.
What this skill does
DDD Full-Project Compliance Audit Deep scan of every Java file against all DDD rules. Use for architecture review, refactoring assessment, or pre-release audit. Trigger Run when user says "full DDD audit", "check entire project", "architecture review", or "DDD compliance report". Workflow Step 1: Discover All Java Files Count files and estimate: "Scanning {N} files across {M} layers..." Step 2: Load All Rule Files Read EVERY rule file at rules/: rules/domain-layer.md rules/application-layer.md rules/adaptor-layer.md rules/infrastructure-layer.md rules/client-layer.md rules/model-layer.md rules/anti-patterns.md Plus reference files if needed: references/base-classes-reference.md references/exception-handling.md Step 3: Layer-by-Layer Audit Group files by layer. For each layer: 1. Package check — all files in correct package? 2. Base class check — all classes extend correct base? 3. Naming check — classes/methods follow DDD naming conventions? 4. Dependency check — no illegal cross-layer imports? 5. Structural check — aggregates, entities, value objects structured correctly? 6. Exception mode check — 阻断型 throws, 分支型 returns ResultDO? Step 4: Cross-Layer Checks Dependency direction: Run grep -r "import org\.bookiosk\.ddd\." on each layer, verify no reverse dependencies Missing patterns: Are there layers with zero classes? Missing base classes? Anemic model detection: Any domain class with only getters/setters and no behavior methods? Exception boundary: Is APP catching Domain/Adaptor exceptions? Is any layer throwing across boundaries? Step 5: Report Format as comprehensive report: Severity Level Criteria --- --- CRITICAL Architecture violation — wrong layer dependency, missing required base class, domain depends on infrastructure HIGH Rule violation — wrong naming, public identity setter, domain service with no behavior MEDIUM Convention deviation — anemic entity, missing Field wrapper, no JavaDoc on public API LOW Style — inconsistent formatting, missing @Override Ke …
How to use it
Reference it in AdaL, Claude Code, Cursor or any coding agent — nothing to install:
@skills aiskillstore/ddd-check-full