ddd-check-incremental
Check Changed Java Code for DDD Compliance
DDD violations in changed Java files can be missed before commits. This skill reviews Git differences by layer and reports focused fixes.
Install with my Agent
Copy this request to your Agent. It includes the canonical Skill page and manifest.
Review the Skillstore skill "ddd-check-incremental" from https://skillstore.io/skills/bookiosk-ddd-check-incremental.md and its manifest at https://skillstore.io/api/skills/bookiosk-ddd-check-incremental/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.
Test it
Using "ddd-check-incremental". Check the staged Java changes before I commit.
Expected outcome:
DDD Check: 3 files changed. Order.java has a critical infrastructure dependency. Move persistence access behind GatewayI. Two other files have no reportable issues.
Using "ddd-check-incremental". Review my changed application and client files.
Expected outcome:
- CreateOrderService.java: High. The command service does not extend ApplicationCmdService. Update the base class.
- OrderDTO.java: High. A domain object is exposed through the DTO. Map it to client-safe fields.
Security Audit
SafeAll 22 static findings are false positives caused by Markdown code fences and inline code formatting. The only executable examples use fixed, read-only Git and grep commands without dynamic input, destructive behavior, or data transmission.
Risk Factors
โ๏ธ External commands (22)
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.
Copy report link
https://skillstore.io/skills/bookiosk-ddd-check-incremental/audits/3?utm_source=security_passport&utm_medium=share&utm_campaign=versioned_reportMarkdown badge
[](https://skillstore.io/skills/bookiosk-ddd-check-incremental?utm_source=security_passport_badge)HTML badge
<a href="https://skillstore.io/skills/bookiosk-ddd-check-incremental?utm_source=security_passport_badge"><img src="https://skillstore.io/badges/skills/bookiosk-ddd-check-incremental/security.svg" alt="Skillstore security assessment" loading="lazy"></a>Embed card
<iframe src="https://skillstore.io/embed/skills/bookiosk-ddd-check-incremental.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-incremental security audit report (audit version 3) [Author version unspecified]. Skillstore. https://skillstore.io/skills/bookiosk-ddd-check-incremental/audits/3BibTeX citation
@techreport{bookiosk-bookiosk-ddd-check-incremental-2026,
author = {bookiosk},
title = {ddd-check-incremental security audit report (audit version 3)},
institution = {Skillstore},
year = {2026},
number = {3},
url = {https://skillstore.io/skills/bookiosk-ddd-check-incremental/audits/3},
note = {Author version unspecified}
}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-incremental security audit report (audit version 3)"
version: "unspecified"
type: report
authors:
- name: "bookiosk"
date-released: "2026-07-13"
url: "https://skillstore.io/skills/bookiosk-ddd-check-incremental/audits/3"
identifiers:
- type: other
value: "skillstore:bookiosk-ddd-check-incremental:audit:3"
description: "Skillstore immutable audit report identifier"
Skillstore Score
Why this score Evidence Confidence: MediumWhat You Can Build
Review Before Commit
Check staged Java changes for DDD violations and receive precise fixes before creating a commit.
Assess Pull Request Changes
Review modified layer boundaries and framework conventions without analyzing unchanged files.
Enforce Team Architecture
Apply shared DDD rules consistently during routine development and identify deviations early.
Try These Prompts
Check my staged Java changes for DDD compliance. Report only real violations and suggest exact fixes.
Review all staged and unstaged Java changes. Classify each file by layer and cite the relevant rule for every violation.
Inspect changed domain Java files for forbidden dependencies, base-class errors, public setters, and exposed infrastructure concerns.
Analyze changed Java files across all DDD layers. Explain dependency violations, severity, architectural impact, and the smallest compliant correction.
Best Practices
- Run the check with a clean understanding of which staged and unstaged changes should be included.
- Keep the referenced layer rules available and aligned with the repository architecture.
- Verify each suggested fix against project requirements before committing.
Avoid
- Do not use this incremental check as a replacement for a complete architecture audit.
- Do not accept severity labels without reviewing the cited rule and source context.
- Do not apply project-specific base-class rules to repositories that use another DDD framework.