consistency-check

Name: consistency-check
Availability: InStock
Author: easonlao

Detect cross-document inconsistencies between GDD definitions and the design registry.

Updated Apr 25, 2026

Search Tags:#registry #consistency check #design validation #gdd #cross-document #grep-first

Ready to run

npx skills add https://github.com/easonlao/jiazi-game --skill consistency-check-easonlao

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: consistency-check
Source: https://github.com/easonlao/jiazi-game/tree/main/.claude/skills/consistency-check
Command: npx skills add https://github.com/easonlao/jiazi-game --skill consistency-check-easonlao

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

It prevents design drift by detecting when GDD documents define conflicting values for the same registered entity, item, formula, or constant.

Core Features & Use Cases

Cross-document consistency scanning: Compares entries in design/registry/entities.yaml against values found in design/gdd/*.md.
Grep-first performance approach: Reads the registry once, then greps for registered names with small context to avoid full document reads unless needed.
Conflict classification and resolution guidance: Produces PASS/CONFLICTS/BLOCKED-style output and identifies stale registry vs unverifiable references.

Use it when you add or edit GDDs to ensure entity stats, item values, formula variables, and constants stay aligned with the authoritative registry.

Quick Start

Run consistency-check for the full design set by asking it to scan all registered entities against all GDDs.

Frequently Asked Questions about consistency-check

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

FAQPage Schema

How do I detect cross-document inconsistencies between GDD definitions and a design registry?▼

Detect cross-document inconsistencies by comparing registered entities, items, formulas, and constants in entities.yaml against values in gdd/*.md files. This scanning process identifies conflicting values for the same registered design element to prevent design drift.

When do I need to run a GDD consistency check?▼

Run a GDD consistency check when adding or editing GDDs, during pre-architecture gating, or on-demand for a specific entity. It ensures entity stats, item values, formula variables, and constants stay aligned with the authoritative registry.

What is the best way to scan large GDD documents for registry mismatches without performance issues?▼

The best way to scan large GDD documents is using a grep-first approach. Load the registry once, then grep for registered names with small context to avoid full document reads unless a conflict requires deep investigation.

Can I check a specific entity or item across all GDD files instead of scanning the full design set?▼

Yes, you can run on-demand checks for a specific entity or item across design/gdd/*.md files. This targets only matching GDD sections rather than requiring a full scan of all registered entities.

What does the consistency check report show when it finds conflicting or stale registry values?▼

The consistency check report outputs structured PASS, CONFLICTS, or BLOCKED classifications. It identifies stale registry entries, unverifiable references, and provides resolution guidance for detected design mismatches.