consistency-check

To check for inconsistencies across GDD Markdown files, compare all entries against a central entity registry to detect conflicting values for entities, items, formulas, and constants. The scan reads the registry once, then greps relevant sections to produce a structured conflict report.

A grep-first approach for conflict detection reads the central entity registry once, then targets only relevant GDD sections using grep. This avoids scanning entire documents, enabling quick cross-document mismatch identification for entities, items, formulas, and constants.

To validate updated game design documents against an entity registry, run a consistency check using modes like full, since-last-review, entity:<name>, or item:<name>. The check locates in-scope GDD Markdown files, greps for registry entries, and reports any mismatches found.

Yes, you can scan for conflicts affecting a single entity or item by using the entity:<name> or item:<name> modes. These targeted modes grep relevant GDD sections specifically for the named entity or item, reporting any conflicting values against the central registry.

A cross-GDD consistency check report includes identified conflicts for entities, items, formulas, and constants, alongside detections of stale registry entries. The final output provides actionable resolution guidance to fix mismatches across the design documents.

You should run a consistency check on your game design documents before architecture reviews to ensure all GDD entries align with the central entity registry. Validating new or updated GDDs early resolves conflicting values before downstream development begins.