review-all-gdds

Identify contradictions, stale references, and design theory violations across game design documents.

14|1|Updated Apr 12, 2026

Search Tags:#git #consistency #design-review #game-design #gdd #cross-document

Ready to run

npx skills add https://github.com/Euraika-Labs/Codex-Code-Game-Studios --skill review-all-gdds-euraika-labs

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: review-all-gdds
Source: https://github.com/Euraika-Labs/Codex-Code-Game-Studios/tree/main/.agents/skills/review-all-gdds
Command: npx skills add https://github.com/Euraika-Labs/Codex-Code-Game-Studios --skill review-all-gdds-euraika-labs

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Game projects with many system GDDs often suffer from hidden contradictions, stale references, and design theory violations that only become apparent when all documents are considered together. This Skill automatically surfaces those issues before architecture begins.

Core Features & Use Cases

Cross‑GDD Consistency Checks: Detects dependency asymmetries, rule contradictions, stale references, ownership conflicts, and formula mismatches across all system GDDs.
Design Theory Review: Identifies competing progression loops, cognitive overload, dominant strategies, economic imbalances, pillar drift, and player‑fantasy conflicts.
Incremental Mode: Optionally reviews only GDDs changed since the last report using Git history.
Parallel Processing: Runs consistency and design‑theory analyses concurrently for speed.

Quick Start

Run $review-all-gdds to generate a comprehensive cross‑GDD review report.

Frequently Asked Questions about review-all-gdds

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

FAQPage Schema

How do I check for contradictions across multiple game design documents?▼

To check for contradictions across game design documents, you can run a cross-document review that detects dependency asymmetries, rule conflicts, stale references, and formula mismatches across all system GDDs before architecture begins.

How does incremental GDD review using git history work?▼

Incremental GDD review using git history works by parsing only the game design documents changed since the last review report, ensuring faster consistency checks by skipping unchanged markdown files.

When do I need a cross-document consistency check for game design?▼

You need a cross-document consistency check for game design when your project has multiple system GDDs and you are entering the pre-architecture phase, requiring holistic validation to surface hidden design theory violations.

Can I detect design theory violations like dominant strategies and economic imbalances in GDDs?▼

You can detect design theory violations like dominant strategies, economic imbalances, competing progression loops, and pillar drift by applying a concurrent design-theory analysis across all your game design documents.

Do I need markdown and git to run a game design document review?▼

You need the ability to parse markdown files in your design/gdd directory to run a game design document review. Git history is optional and only required if you want to utilize the incremental review mode for changed files.