consistency-check

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

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

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Game design documents written across multiple sessions drift apart: the same entity gets different stats, items get different values, and formulas get different variables in different GDDs. This Skill catches those contradictions before they poison architecture decisions. ## Core Features & Use Cases - Registry-Driven Scanning: Loads the entity registry (entities, items, formulas, constants) 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 based on the registry source field. - Scoped Modes: Run a full scan, check only GDDs modified since the last review, or target a single entity or item by name. - Use Case: After writing a new economy GDD, run the check to confirm item gold values match what the combat GDD already registered, and log any conflicts to the consistency failure log before starting architecture work. ## Quick Start Use $ai-game-studio:consistency-check 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, which loads design/registry/entities.yaml and greps each registered name across design/gdd Markdown files. It compares extracted attribute values against the registry and reports conflicts with the authoritative source document.

How do I check consistency for just one entity or item?

Pass a scoped argument such as entity:<name> or item:<name> to limit the scan to that single registry entry across all GDDs. A since-last-review mode also restricts scanning to GDDs modified after the most recent review report.

When should I run a GDD consistency check?

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

What happens if the entity registry is empty or missing?

The check stops immediately and reports that the registry is empty, since the registry is populated automatically after each GDD is completed by the design-system workflow. There is nothing to compare until at least one GDD has been written.

Does the consistency check modify the registry automatically?

No. It asks for confirmation before updating stale registry entries or adding new cross-system entries, and it never deletes entries. Removed entries are marked with status deprecated, and every conflict is appended to docs/consistency-failures.md.