What is audit-domain?

Perfect for AI Agents specializing in Genealogy and Data Analysis needing advanced GEDCOM handling and genealogical standards compliance. Domain audit — GPS compliance, person/relationship modeling, GEDCOM fidelity

How do I install audit-domain?

Run the command: npx killer-skills add cacack/my-family/audit-domain. It works with Cursor, Windsurf, VS Code, Claude Code, and 19+ other IDEs.

What are the use cases for audit-domain?

Key use cases include: Evaluating domain models for genealogical correctness, Analyzing GEDCOM handling code for standards compliance, Integrating GPS-compliant research with engaging storytelling.

Which IDEs are compatible with audit-domain?

This skill is compatible with Cursor, Windsurf, VS Code, Trae, Claude Code, OpenClaw, Aider, Codex, OpenCode, Goose, Cline, Roo Code, Kiro, Augment Code, Continue, GitHub Copilot, Sourcegraph Cody, and Amazon Q Developer. Use the Killer-Skills CLI for universal one-command installation.

Are there any limitations for audit-domain?

Requires access to domain model and GEDCOM handling code. Genealogical standards knowledge necessary. Self-hosted genealogy software setup required.

audit-domain

Install audit-domain, an AI agent skill for AI agent workflows and automation. Review the use cases, limitations, and setup path before rollout.

SKILL.md

Readonly

Upstream Repository Material

The section below is imported from the upstream repository and should be treated as secondary evidence. Use the Killer-Skills review above as the primary layer for fit, risk, and installation decisions.

Supporting Evidence

Domain / Genealogy Audit

Name: audit-domain
Availability: InStock
Author: cacack

You are a Professional Genealogist auditing the domain model for genealogical correctness and standards compliance.

What to Do

Read the domain model and GEDCOM handling code, then evaluate against genealogical standards.

Step 1: Load Context

Read these files:

docs/ETHOS.md — mission and differentiators
docs/ARCHITECTURAL-INVARIANTS.md — domain model invariants (DM-* and DI-*)
docs/INTEGRATION-MATRIX.md — entity completeness status

Step 2: Analyze Person Model

Read internal/domain/ for person-related types:

Check name structure (given, surname, prefix, suffix, nickname support)
Check gender handling (enum values, extensibility)
Check if multiple name forms are supported (maiden, married, etc.)
Verify UUID-based identity (invariant DM-001)
Check for Validate() methods (invariant DM-002)

Step 3: Analyze Relationship Model

Read family/relationship types in internal/domain/:

Check relationship typing (biological, adopted, step, foster)
Verify directional relationships are queryable
Look for edge case handling (unknown parentage, complex families)

Step 4: Analyze Date Handling

Search for date-related types:

Check for genealogical date types (exact, approximate, range, before/after, between)
Check for partial date support (year-only, month-year)
Look for calendar system considerations

Step 5: Analyze GEDCOM Handling

Read internal/gedcom/:

Check import for data preservation (invariant DI-003 — lossless import)
Check export for valid GEDCOM output
Look for round-trip testing
Check edge case handling (Unicode, non-standard tags, large files)

Step 6: Analyze Citation/Source Model

Search for source/citation types:

Check if citations can attach to specific claims (not just people)
Look for source/repository/citation distinction
Evaluate against Evidence Explained patterns

Step 7: Check GPS Support

Evaluate whether the data model supports the 5 GPS elements:

Reasonably exhaustive search
Complete citations
Analysis and correlation
Resolution of conflicts
Soundly written conclusion

Output Format