consistency-check

To check for stale registry entries, scan your GDD files for changed source values and compare them against the central registry. The process identifies pending updates and produces a review-ready report with actionable recommendations for synchronizing the registry or source GDDs.

The best way to validate entity attributes across multiple GDD files is running a consistency check that targets only the sections mentioning registered names. It extracts nearby attributes, flags conflicts across entities and items, and outputs a review-ready conflict report without reading entire documents.

Yes, you can filter consistency checks to target a specific entity or item in your GDDs. By applying optional filters like entity:<name> or item:<name>, the check limits its grep-first scan to relevant sections, producing a focused conflict report for the specified registry entries.

To identify stale registry entries when source GDD values have changed, run a consistency check across your design GDDs. It compares current source values against the central entity registry, flags mismatches, and generates a report with suggested registry updates to restore synchronization.

No, a grep-first consistency check does not require full-document reads of every GDD. It reads the registry once, scans only the GDD sections that mention registered names, and avoids full reads entirely unless a specific conflict requires deeper investigation.