consistency-check

Compare GDD files against the entity registry to detect cross-document inconsistencies.

14|1|Updated Apr 12, 2026

Search Tags:#consistency #validation #registry #grep #design-docs #gdd

Ready to run

npx skills add https://github.com/Euraika-Labs/Codex-Code-Game-Studios --skill consistency-check-euraika-labs

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: consistency-check
Source: https://github.com/Euraika-Labs/Codex-Code-Game-Studios/tree/main/.agents/skills/consistency-check
Command: npx skills add https://github.com/Euraika-Labs/Codex-Code-Game-Studios --skill consistency-check-euraika-labs

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Scans GDDs against the entity registry to detect cross-document inconsistencies: a single entity with divergent stats, an item with conflicting values, or a formula defined with incompatible variables. It uses a grep-first approach to minimize full-document reads by loading the registry first and targeting only the sections that mention registered names.

Core Features & Use Cases

GDD consistency scanning: compares registered entities, items, formulas, and constants across all design/gdd *.md files.
Conflict reporting: generates a report of mismatches with references to the authoritative registry source.
Workflow integration: flags stale registry entries and guides the resolution process to align GDDs with the registry.
Use Case: when a new GDD is added or an existing one is updated, run this skill to surface cross-document inconsistencies before architecture decisions.

Quick Start

Run the consistency-check to scan all GDDs for cross-document inconsistencies.

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 across my game design docs?▼

Run a consistency check to compare registered entities, items, formulas, and constants across all design/gdd/*.md files. This grep-first scan targets only sections mentioning registered names to detect divergent stats, conflicting item values, or incompatible formula variables.

How does a grep-first workflow validate GDD consistency?▼

A grep-first workflow validates GDD consistency by loading the entity registry at design/registry/entities.yaml first, then scanning design docs for matches. It collects context around matches to report conflicts and flags stale registry entries for review without reading full documents.

What is the best way to detect conflicting entity stats in game design documents?▼

The best way to detect conflicting entity stats is to cross-reference your design docs against an authoritative registry. Comparing registered entities, items, and constants across all GDD sources surfaces mismatches and generates a report referencing the authoritative registry source.

Do I need an entity registry to scan GDDs for mismatches?▼

Yes, you need an entity registry at design/registry/entities.yaml to scan GDDs for mismatches. The registry provides the authoritative source values required to detect divergent stats, conflicting item values, and incompatible formula variables across your design/gdd/*.md files.

When should I run a consistency check on my design docs?▼

Run a consistency check on your design docs when a new GDD is added or an existing one is updated. This surfaces cross-document inconsistencies before architecture decisions, flagging stale registry entries and guiding the resolution process to align GDDs with the registry.