Consistency Check

Before you start: read this whole install prompt, tell me in a few lines what this skill does and what installing it involves, and wait for my go-ahead before you do anything else. Prerequisites — INTEGRATED SYSTEM FIRST: this skill is one piece of the complete "Claude Code Game Studios" template (49 agents, 74 skills, studio templates and a studio CLAUDE.md, per the repository README). Each skill assumes that template is installed, with its conventions, its project.yaml / project.local.yaml configuration, its .claude/docs/ mode documents, its hooks (for example hooks/yaml-helper.sh, outside this skill's folder) and its .claude/scripts/ helpers. Installing this listing alone copies only this skill's folder, without the rest of the system: the skill may reference template agents, files, hooks or scripts that are absent outside the full template, and it may not run as designed on its own. No account, no key and no payment are needed to copy the files, and nothing is run during installation. Install "Consistency Check" for me. It is the Game Studios cross-document consistency check. It loads the entity registry (design/registry/entities.yaml) once, builds entity, item, formula and constant lookup tables, then grep-scans the in-scope GDDs under design/gdd/ for those registered names (with -C 3 context, no full reads unless a conflict needs investigation), comparing every stated value against the registry and classifying conflicts, stale registry entries (the source GDD moved, the registry did not) and unverifiable mentions. Modes: full, since-last-review (git log over design/gdd/), entity:<name> and item:<name>; at the standard workflow tier only hits under required GDD sections are compared, the rest are listed as not checked. An empty registry, an unregistered name or zero GDDs in scope ends in NOT ASSESSED. Corrections are gated: it re-reads the registry before each edit, asks before updating it or adding entries, never deletes entries (it deprecates them), validates with the template's .claude/scripts/registry.sh, asks before appending conflicts to docs/consistency-failures.md, and silently appends its one-line breadcrumb to production/session-state/active.md. Repository: https://github.com/Donchitos/Claude-Code-Game-Studios (the skill is the whole .claude/skills/consistency-check/ folder at the pinned commit: 1 files in total) Pinned version: install the code at commit 05ad7c8a5b8aa2aa86bbd3439ae7cf7295cac418 exactly. Do not substitute a newer version. If this commit is unreachable, stop and tell me. 1. Clone https://github.com/Donchitos/Claude-Code-Game-Studios into a temporary folder, check out commit 05ad7c8a5b8aa2aa86bbd3439ae7cf7295cac418, and copy the .claude/skills/consistency-check/ folder from that checkout. Then compare every file in the folder with the fingerprints recorded for this listing on 2026-10-22: [FINGERPRINTS] - SKILL.md: SHA-256 be7697de6ff3b8b38b0078c7fa9a71eafe87cc04d008db7192a0439e3d000228 If a file does not match, it changed since the listing was prepared: do not install it yet, tell me what you found and let me decide. 2. Read SKILL.md in full, and tell me in plain words: what the skill does when used, what it connects to, whether it reads or sends any personal information or credentials, and anything that seems unusual. Stop on any red flag and tell me before going further. Confirm these points from the files: - The skill folder holds 1 file only: SKILL.md (15217 characters of instructions in a single file; there are no companion files in its folder). Nothing in the folder is run during installation; companion files are instructions/references the skill reads at use time, copied as-is. - Nothing is sent anywhere during installation itself; the only download at install time is the skill folder from GitHub at the pinned commit, and no project of mine is read or modified. - Integrated-system reality, from the files: at use time the skill resolves studio configuration by running the template's hooks/yaml-helper.sh (keys automation, workflow, system_overrides), follows the template's .claude/docs/automation-modes.md and workflow-modes documents, runs git log over design/gdd/ in since-last-review mode, and validates registry writes with the template's .claude/scripts/registry.sh — files and scripts that live outside this skill's folder and are absent in a standalone install, so parts of it cannot run outside the full template. Inside the template it works on my project's own GDDs and registry, locally. - At use time it writes only in my own project and, except for one disclosed exception, only after asking: registry corrections and additions to design/registry/entities.yaml and conflict entries in docs/consistency-failures.md are each asked about first; the exception is the silent one-line breadcrumb it appends to production/session-state/active.md at the end of a run, which the file states it does silently. No account, key, payment or third-party service is named in the files I read. - Do not scan any GDD, do not run git, the registry script or any template hook, and do not use the skill in any way during this install: using it is a separate step that only starts when I ask for it later. 3. When I say "yes, install", install it as a skill: copy the whole consistency-check folder into the agent's skills directory, in a folder named exactly "consistency-check", keeping its 1 files in their original relative layout (SKILL.md at its root). 4. Verify with no network calls: frontmatter valid (name: consistency-check), the 1 files in place with matching fingerprints. Do not run anything from the folder and do not use the skill to verify. 5. Report what was installed, where, and what I still need to do myself (for example: that it belongs to the full Claude Code Game Studios template and may not run standalone (it resolves its settings through the template's yaml-helper hook and validates with the template's registry script), and that inside the template it compares my GDDs to my entity registry locally, asking before it corrects the registry or logs a conflict). GitHub is optional: if I have a GitHub account or the gh CLI, you may use it; otherwise public access is fine. Never require it unless it's in the prerequisites above. Rules: don't touch anything outside the temp folder and the install target. If anything looks off, stop and ask me.