consistency-check

Detect cross-document inconsistencies between GDDs and the entity registry using grep-first scanning.

Updated Aug 2, 2026
One-click install
npx skills add https://github.com/claretagrapelike32/codex-ai-game-studio --skill consistency-check-claretagrapelike32
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: consistency-check
Source: https://github.com/claretagrapelike32/codex-ai-game-studio/tree/main/plugins/ai-game-studio/skills/consistency-check
Command: npx skills add https://github.com/claretagrapelike32/codex-ai-game-studio --skill consistency-check-claretagrapelike32

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Game design documents drift apart as they are written: the same entity gets different stats, items get different values, and formulas get different variables across GDDs. This Skill catches those contradictions before they poison architecture decisions. ## Core Features & Use Cases - Registry-driven scanning: Loads design/registry/entities.yaml and greps only the GDD sections mentioning registered names instead of reading full documents. - Conflict classification: Distinguishes hard conflicts, stale registry entries, and unverifiable references, then proposes which document is authoritative. - Registry maintenance: Updates stale entries, logs conflicts to docs/consistency-failures.md, and records session state. - Use Case: After writing a new combat GDD, run the check to confirm its damage formula and item values match what the economy GDD already registered. ## Quick Start Run the consistency-check skill to scan all GDDs against the entity registry and report any conflicting values.

Frequently Asked Questions about consistency-check

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

FAQPage Schema
How do I check GDDs for inconsistent entity values?

Run the consistency check after writing each GDD. It loads the entity registry, greps each GDD for registered names, and compares extracted attributes against registry values, reporting conflicts with the authoritative source document.

What is an entity registry in game design documentation?

An entity registry is a YAML file (design/registry/entities.yaml) recording canonical values for entities, items, formulas, and constants across GDDs. It is populated automatically as GDDs are written and serves as the single source of truth for cross-document checks.

Can I check consistency for just one entity or item?

Yes. Pass an argument like entity:<name> or item:<name> to scope the scan to a single entry across all GDDs. A since-last-review mode also limits scanning to GDDs modified since the previous review report.

When should I run a GDD consistency check?

Run it after writing each new GDD, before a holistic design review, and before creating architecture decision records. Catching conflicts early prevents inconsistent values from propagating into downstream technical design.

What happens when the registry itself is out of date?

The check flags stale registry entries separately from true conflicts. With your approval it updates the registry value, records the old value as a comment, and never deletes entries—removed entries are marked deprecated instead.