consistency-check

Detect cross-document inconsistencies between game design documents and the central entity registry.

Updated Jul 16, 2026
One-click install
npx skills add https://github.com/johnatas-henrique/overdrive --skill consistency-check-johnatas-henrique
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: consistency-check
Source: https://github.com/johnatas-henrique/overdrive/tree/main/.opencode/skills/consistency-check
Command: npx skills add https://github.com/johnatas-henrique/overdrive --skill consistency-check-johnatas-henrique

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Game design documents (GDDs) often contain conflicting values for the same entities, items, formulas, or constants across different files, leading to broken game mechanics, wasted development time, and costly rework when these inconsistencies are caught late in the development cycle.

Core Features & Use Cases

  • Cross-Document Conflict Detection: Scans all GDDs against the central entity registry to flag mismatched stats, values, and formula variables.
  • Targeted or Full Audits: Supports checking a single specific entity/item or running a full audit of all registered entries across all GDDs.
  • Traceable Conflict Logging: Automatically logs all detected conflicts to a dedicated failure log for team visibility and historical tracking. Use case: A game designer can run this skill immediately after finishing a new combat system GDD to ensure all entity stats match the values defined in the core registry before moving on to architecture work.

Quick Start

Run the consistency-check skill after completing any new game design document to scan for cross-document value conflicts and get a clear report of any issues to resolve.

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 values?

You can check game design documents for conflicting values by scanning all GDDs against a central entity registry to flag mismatched entity stats, item values, and formula variables before architecture work.

What causes inconsistencies across game design documents?

Inconsistencies across game design documents happen when conflicting values for the same entities, items, or constants are entered across different files, poisoning downstream architecture and causing broken game mechanics.

Can I run a conflict detection audit on a single entity?

Yes, you can run conflict detection on a single entity by performing a targeted audit of a specific item, or you can execute a full audit to scan all registered entries across all GDDs.

How do I log design validation errors in game development?

You log design validation errors in game development by using automated conflict logging to record detected cross-document inconsistencies to a dedicated failure log for team visibility and historical tracking.

When should I run a cross-document consistency check?

You should run a cross-document consistency check immediately after finishing a new game design document to ensure all entity stats match the core registry before moving on to architecture work.