x-review-data-modeling

Review domain-model changes for DDD alignment and data-model correctness.

Updated Aug 23, 2026
One-click install
npx skills add https://github.com/edercnj/ia-dev-environment --skill x-review-data-modeling
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: x-review-data-modeling
Source: https://github.com/edercnj/ia-dev-environment/tree/main/src/main/resources/claude/skills/x-review-data-modeling
Command: npx skills add https://github.com/edercnj/ia-dev-environment --skill x-review-data-modeling

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Data-modeling specialists need a structured, repeatable process to validate domain-model changes against DDD principles, ensuring entities, aggregates, value objects, and repositories align with a coherent domain model and persistence strategy.

Core Features & Use Cases

  • Verify entity identity and lifecycle within aggregates, ensuring no orphaned entities.
  • Check aggregate boundaries, cross-aggregate references via IDs, and invariants enforcement in the domain layer.
  • Assess domain-to-persistence mapping with dedicated mappers and ensure domain events are modeled and persisted appropriately.

Quick Start

Convert the latest PR changes into a domain-model review request and generate a structured report.

Frequently Asked Questions about x-review-data-modeling

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

FAQPage Schema
How do I review domain models for DDD alignment in a pull request?▼

To review domain models for DDD alignment, analyze the PR's touched domain layer code to validate entity identity, aggregate boundaries, value object immutability, and domain-persistence mappings, generating a structured report with actionable remediation.

How do I validate aggregate boundaries and cross-references in domain-driven design?▼

Validating aggregate boundaries in domain-driven design involves checking that cross-aggregate references use IDs rather than direct object references and ensuring the domain layer correctly enforces invariants within each aggregate.

What is the best way to check domain-to-persistence mapping for entities and value objects?▼

The best way to check domain-to-persistence mapping is to verify dedicated mappers handle the conversion, ensuring value objects remain immutable and domain events are modeled and persisted appropriately.

Can I audit repository implementations and domain events handling during code review?▼

Yes, you can audit repository implementations and domain events handling during code review by validating the touched domain layer code for correct identity patterns, lifecycle management, and appropriate persistence strategies.

Why do I need to verify entity identity and lifecycle within aggregates?▼

You need to verify entity identity and lifecycle within aggregates to prevent orphaned entities, ensuring a coherent domain model where all data modeling changes align with strict DDD principles and invariant enforcement.