consistency-check

Scan GDD markdown files against the entity registry and report conflicting values.

72|7|Updated Apr 29, 2026

Search Tags:#consistency #registry #game design #design governance #gdd #cross-document validation #grep scanning

Ready to run

npx skills add https://github.com/striderZA/OpenCodeGameStudios --skill consistency-check-striderza

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: consistency-check
Source: https://github.com/striderZA/OpenCodeGameStudios/tree/main/.opencode/skills/consistency-check
Command: npx skills add https://github.com/striderZA/OpenCodeGameStudios --skill consistency-check-striderza

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

OpenGameStudios helps coordinate large game-design documents, but entity/item/formula values can drift across multiple GDDs, causing downstream architecture and implementation mistakes.

Core Features & Use Cases

Cross-document consistency scanning: Compares GDD mentions of registered entities/items/formulas/constants against the authoritative design/registry/entities.yaml.
Grep-first performance strategy: Uses targeted Grep with limited context to avoid full document reads unless a conflict requires investigation.
Conflict reporting with remediation guidance: Produces a conflict/staleness/unverifiable report and can update the registry for stale entries, then logs failures for traceability.

Quick Start

Run the consistency check for everything in the current design by asking your assistant: "Execute /consistency-check full."

Frequently Asked Questions about consistency-check

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

FAQPage Schema

How do I check game design documents for conflicting entity values?▼

Cross-document consistency scanning compares mentions of registered entities, items, formulas, and constants in your GDD markdown files against an authoritative centralized entity registry to detect and report conflicting values.

How do I run a full consistency audit across multiple GDD files?▼

Run a full consistency audit by loading the centralized entity registry, locating all in-scope GDD markdown files, and executing a grep-first extraction to compare context and flag stale or conflicting attribute values across the documents.

What is the best way to find stale entity registry entries in game design?▼

The best way to find stale entity registry entries is to perform targeted consistency checks by entity or item name, which scans GDD mentions and offers registry corrections for entries that have drifted from the authoritative values.

Can I use grep scanning to validate cross-document GDD consistency without reading full files?▼

Yes, you can use grep scanning to validate cross-document GDD consistency by performing targeted Grep with limited context to extract nearby attribute and value context, avoiding full document reads unless a conflict requires deep investigation.

Does consistency checking work for incremental scans since the last design review?▼

Yes, consistency checking works for incremental scans since the last review by locating in-scope GDD markdown files and running targeted grep-first extraction to identify any new conflicting values introduced since the previous audit.

What formats do I need to set up for cross-document game design validation?▼

To set up cross-document game design validation, you need an authoritative entity registry formatted as a YAML file and your game design documents stored as markdown files under a designated design directory structure.