Agent skill · software engineering · aiskillstore

ddd-check-incremental

Incremental DDD compliance check — scans only changed/new Java files in git diff and validates against DDD layer rules. Use before every commit.

Why this skill is useful

Adds a script that automates DDD compliance checks for Java files, ensuring adherence to specific architectural rules not commonly found in public documentation.

What it needs

Requires git installed locally. About 3k tokens when loaded. Last updated 2026-08-07. 405 stars on the source repository.

What this skill does

DDD Incremental Compliance Check Check only new or modified Java files against DDD layer rules. Fast, pre-commit focused. Trigger Run when user says "check my changes", "DDD check", "review this code", or before committing. Workflow Step 1: Find Changed Files If no Java files changed, report: "No Java files changed — nothing to check." Step 2: Classify Each File by Layer Map file path to DDD layer: Package Pattern Layer Rule File --- --- --- /ddd/common/ Common (structural rules only) /ddd/domain/ Domain rules/domain-layer.md /ddd/application/ Application rules/application-layer.md /ddd/adaptor/ Adaptor rules/adaptor-layer.md /ddd/infrastructure/ Infrastructure rules/infrastructure-layer.md /ddd/client/ Client rules/client-layer.md /ddd/model/ Model rules/model-layer.md Step 3: Read Relevant Rule Files Load only the rule files matching the changed layers. Plus always load rules/anti-patterns.md. Step 4: Check Each Changed File For each changed file, read it and validate against: 1. Structural rules — correct base class, correct package, correct naming 2. Dependency rules — no forbidden imports (e.g. domain must not import infrastructure) 3. Anti-patterns — cross-check against rules/anti-patterns.md Step 5: Report Format output as: Severity Level Criteria --- --- CRITICAL Architecture violation — wrong layer dependency, missing base class, domain depends on infrastructure HIGH Rule violation — wrong naming, public setter on aggregate, wrong exception mode MEDIUM Convention deviation — missing JavaDoc, wrong file location LOW Style suggestion Key Checks Domain Layer (MOST CRITICAL): [ ] All aggregates extend BaseAggregate<ID> [ ] All entities extend BaseEntity<ID> [ ] All value objects extend BaseValue [ ] setId() is protected, not public [ ] No infrastructure imports (no Mapper, no JPA, no SQL) [ ] Repository interfaces extend AggregateRepository<T, ID, Q> [ ] External calls go through GatewayI interfaces [ ] Aggregate methods = business behaviors, not CRUD [ ] Desig …

How to use it

Reference it in AdaL, Claude Code, Cursor or any coding agent — nothing to install:

@skills aiskillstore/ddd-check-incremental

View the source on GitHub

Browse the @skills marketplace