consistency-check

Detect cross-document inconsistencies between GDDs and the entity registry.

Updated Mar 26, 2026

Search Tags:#consistency #registry #grep #design-review #gdd #conflict-detection

Ready to run

npx skills add https://github.com/LordKuper/agentic-game-studio --skill consistency-check-lordkuper

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: consistency-check
Source: https://github.com/LordKuper/agentic-game-studio/tree/main/.claude/skills/consistency-check
Command: npx skills add https://github.com/LordKuper/agentic-game-studio --skill consistency-check-lordkuper

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Detects cross-document inconsistencies by comparing all GDDs against the entity registry (design/registry/entities.yaml). Uses a grep-first approach — reads the registry once, then targets only the GDD sections that mention registered names — no full document reads unless a conflict needs investigation.

Core Features & Use Cases

Grep-first conflict scanning across registered entities, items, formulas, and constants.
Provides guidance for conflict resolution, including source-of-truth and registry staleness checks.
Output includes a structured consistency report with potential corrections to the registry and GDDs.

Quick Start

Run the consistency-check after creating or updating a GDD to surface cross-document conflicts.

Frequently Asked Questions about consistency-check

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

FAQPage Schema

How do I find cross-document inconsistencies between my game design documents?▼

To find cross-document inconsistencies, compare all GDDs against the entity registry using a grep-first workflow. This approach reads the registry once and targets only sections mentioning registered names, surfacing conflicts efficiently without requiring full document reads.

What is a grep-first conflict detection workflow for a game design registry?▼

A grep-first conflict detection workflow reads the entity registry once, then searches GDDs for registered names to locate mismatches. It avoids full document reads unless a specific conflict needs investigation, ensuring source-of-truth alignment across items, formulas, and constants.

How do I check my entity registry for stale entries and design conflicts?▼

Check your entity registry for stale entries by running a consistency-check after creating or updating a GDD. This generates a structured consistency report that tracks registry staleness, identifies conflicts, and provides guidance for resolving source-of-truth mismatches.

Does consistency-check work without external dependencies?▼

Yes, consistency-check works without external dependencies. It uses a grep-first approach to scan registered entities, items, formulas, and constants across multiple GDDs, requiring only the entity registry file and the design documents to operate.

When should I run a consistency report for game design documents?▼

Run a consistency report immediately after creating or updating a GDD. This surfaces cross-document conflicts early, tracks stale registry entries, and provides structured guidance for potential corrections to both the GDDs and the registry.

What is the best way to enforce source-of-truth alignment across multiple game design documents?▼

The best way to enforce source-of-truth alignment is using a grep-first scanning workflow against the entity registry. This targets registered names across GDDs, detects conflicts without full reads, and generates a structured report with potential corrections.