consistency-check

Detect cross-document inconsistencies by running a consistency check that greps relevant lines from design GDDs and builds lookup maps from registry YAML files to surface stat conflicts, stale entries, and unverifiable references.

The best way to validate GDD entries is using a grep-first conflict detection approach that scans design markdown files against registry data, producing a structured consistency report with actionable resolutions for any mismatched variables or values.

Yes, you can run a consistency check targeting specific scope using modes like entity:<name> or item:<name>, alongside full checks or since-last-review modes to limit validation to relevant design GDDs and registry entries.

Grep-first conflict detection works by minimizing full document reads, extracting only relevant lines from GDDs and registry YAML files to build lookup maps, then performing phase-based deep investigation only on the conflicts found.

A GDD consistency check reports same entities with different stats, same items with different values, same formulas with different variables, stale registry entries, and unverifiable references across design documents.

No dependencies or external components are required to run a game design document consistency check; it operates directly on in-scope design GDD markdown files and registry YAML data to validate data integrity.