Detect cross-document inconsistencies between GDD files and the entity registry.
npx skills add https://github.com/dnkrow/skill --skill consistency-check-dnkrow
Please help me install this Agent Skill. Skill: consistency-check Source: https://github.com/dnkrow/skill/tree/main/claude-global/consistency-check Command: npx skills add https://github.com/dnkrow/skill --skill consistency-check-dnkrow
It prevents design drift by finding entities, items, formulas, and constants that disagree across multiple GDD documents, so downstream architecture decisions don’t get poisoned by contradictions.
Run /consistency-check in full mode to scan all registered entries against all design/gdd/*.md files and get a conflict report.
High-intent search queries and answers about installing and using this skill.
Cross-document consistency checking scans GDD files against an entity registry to detect contradictions. It compares registered entities, items, formulas, and constants to find where the same named element has different stats across documents.
Preventing design drift requires cross-document validation that catches conflicting stats and values before architecture begins. This tool identifies disagreements across multiple GDDs so downstream decisions aren't poisoned by contradictions.
Validating shared stats across GDD markdown files requires loading a central entity registry and scanning documents with targeted grep. This extracts relevant context to compare declared values against registered constants and formulas.
Cross-document validation uses a grep-first approach that loads the registry once and searches only relevant GDD snippets. It performs deep reads exclusively for detected conflicts, avoiding the need to fully read every document.
The consistency checker requires a populated entity registry at design/registry/entities.yaml. Without this baseline file containing registered entities, items, formulas, and constants, there is no reference to validate the GDD markdown files against.
The conflict report provides a clear PASS or CONFLICTS status. For failures, it includes deep investigation steps for the detected conflicts and optional registry correction guidance to resolve the design drift.
easonlaoDetect cross-document inconsistencies between GDD definitions and the design registry.
SjdjdiejdrirhdkjejDetect and resolve dependency conflicts across npm, pip, cargo, and composer.
WindXRanCompare GDD definitions against a central entity registry to detect inconsistencies.
striderZAScan GDD markdown files against the entity registry and report conflicting values.
