Skills ddd-check

📦

ddd-check

Name: ddd-check
Author: bookiosk

v2.0 Content revision r2 Safe 🌐 Network access📁 Filesystem access⚙️ External commands

Audit Java Projects for DDD Compliance

Java architecture can drift across layers, dependencies, and domain models. This skill reviews recent changes or entire projects against practical DDD rules.

Supports: Claude Codex Code(CC)

🥉 78 Bronze

Install with my Agent

Copy this request to your Agent. It includes the canonical Skill page and manifest.

Agent request

Review the Skillstore skill "ddd-check" from https://skillstore.io/skills/bookiosk-ddd-check.md and its manifest at https://skillstore.io/api/skills/bookiosk-ddd-check/manifest. Verify the artifact. You may proceed after verification, subject to the environment's own policy.

Your Agent should still show its plan and request any confirmation required by the security policy.

Agent-readable resources

Use these links when an AI agent, crawler, or script needs clean context instead of reading the full page.

Markdown detail GET /skills/bookiosk-ddd-check.md Signed manifest GET /api/skills/bookiosk-ddd-check/manifest Signed lockfile GET /api/skills/bookiosk-ddd-check/lockfile

Test it

Using "ddd-check". Check my staged Java changes for DDD compliance.

Expected outcome:

High: The domain service imports an infrastructure mapper, which reverses the allowed dependency direction.
Fix: Depend on a domain repository interface and move the mapper access into the infrastructure implementation.

Using "ddd-check". Run a full DDD audit and summarize the weakest layer.

Expected outcome:

The domain layer has the lowest compliance score. Its main issues are public identity setters, anemic aggregates, and infrastructure dependencies.

Using "ddd-check". Review the order application layer and suggest priorities.

Expected outcome:

Critical: Remove direct infrastructure dependencies from application services.
High: Move business invariants from orchestration services into the order aggregate.
Medium: Rename query methods to express clear intent.

Security Audit

Safe

v4 • 7/23/2026 Open versioned report

All 70 static findings are false positives caused by license links, Markdown formatting, Java Mapper examples, architecture prose, or fixed read-only repository commands. No prompt injection, exfiltration, destructive command, reconnaissance behavior, or malicious intent was found.

Files scanned

5,620

Lines analyzed

Review items

False positives ignored

No confirmed security findings were detected by the latest completed static and semantic audit. This does not prove the skill has no side effects.

Audited by: codex View Audit History →

Share & cite this report

Share the versioned assessment report, neutral badge, embed card, and citations. Skillstore reports evidence without deciding whether this Skill is safe.

Open versioned report

Copy report link

https://skillstore.io/skills/bookiosk-ddd-check/audits/4?utm_source=security_passport&utm_medium=share&utm_campaign=versioned_report

Markdown badge

[![Skillstore security assessment](https://skillstore.io/badges/skills/bookiosk-ddd-check/security.svg)](https://skillstore.io/skills/bookiosk-ddd-check?utm_source=security_passport_badge)

HTML badge

<a href="https://skillstore.io/skills/bookiosk-ddd-check?utm_source=security_passport_badge"><img src="https://skillstore.io/badges/skills/bookiosk-ddd-check/security.svg" alt="Skillstore security assessment" loading="lazy"></a>

Embed card

<iframe src="https://skillstore.io/embed/skills/bookiosk-ddd-check.html" title="Skillstore Security Assessment" sandbox="allow-popups allow-popups-to-escape-sandbox" loading="lazy" referrerpolicy="no-referrer" width="420" height="180"></iframe>

Academic citations (APA · BibTeX · CFF)

APA citation

bookiosk. (2026). ddd-check security audit report (audit version 4) [Author version 2.0]. Skillstore. https://skillstore.io/skills/bookiosk-ddd-check/audits/4

BibTeX citation

@techreport{bookiosk-bookiosk-ddd-check-2026,
  author = {bookiosk},
  title = {ddd-check security audit report (audit version 4)},
  institution = {Skillstore},
  year = {2026},
  number = {4},
  url = {https://skillstore.io/skills/bookiosk-ddd-check/audits/4},
  note = {Author version 2.0}
}

CITATION.cff

cff-version: 1.2.0
message: "If you use this Skill, cite its author and this versioned security audit report."
title: "ddd-check security audit report (audit version 4)"
version: "2.0"
type: report
authors:
  - name: "bookiosk"
date-released: "2026-07-23"
url: "https://skillstore.io/skills/bookiosk-ddd-check/audits/4"
identifiers:
  - type: other
    value: "skillstore:bookiosk-ddd-check:audit:4"
    description: "Skillstore immutable audit report identifier"

Skillstore Score

Why this score Evidence Confidence: Medium

Architecture

Maintainability

Content

Community

Spec Compliance

What You Can Build

Review a Feature Branch

Check changed Java files before commit and receive focused DDD violations with practical fixes.

Audit Layer Boundaries

Evaluate dependencies, package placement, domain behavior, and exception boundaries across a complete project.

Prioritize Architecture Work

Use severity-ranked findings and layer scores to plan remediation across teams and releases.

Try These Prompts

Check Recent Changes

Check my changed Java files for DDD compliance. Report only violations, cite the relevant rule, and provide a specific fix.

Review One Layer

Review the {layer} layer in {project_path}. Check package placement, naming, base classes, dependencies, and exception handling.

Run a Full Architecture Audit

Run a full DDD compliance audit of this Java project. Score each layer, identify cross-layer violations, and rank remediation work by severity.

Trace an Aggregate Workflow

Audit the {aggregate_name} workflow end to end. Trace dependencies across layers, detect anemic modeling, and evaluate transaction and exception boundaries.

Best Practices

State whether the review should cover changed files, one layer, or the entire project.
Provide project-specific base classes, naming rules, and approved architecture exceptions.
Verify high-severity findings against source context before scheduling remediation.

Avoid

Do not apply the supplied Java conventions unchanged to unrelated languages or architectures.
Do not treat a compliance score as proof of runtime correctness or complete domain modeling.
Do not request an incremental review when unchanged project files must also be evaluated.