Loading skill
Install any skill in seconds. Free to start, no credit card required.
Get Started Free →donchitos/consistency-check
Scan all GDDs against the entity registry to detect cross-document inconsistencies: same entity with different stats, same item with different values, same formula with different variables. Grep-first approach — reads registry then targets only conflicting GDD sections rather than full document reads.
Passed 18 of 20 test cases with the skill, and 4 of 20 without it.
and 19 more in the full report
14 fixed4 passed either way2 still failing0 broke5 errored
Tokens, turns and time describe resource use, not a dollar price.
One of 14 test cases the skill fixed. Same model, same prompt, with and without the skill.
At the end of a consistency check execution, what specific Markdown comment string and file path must be recorded in `production/session-state/active.md`?
| Checked | Without skill | With skill |
|---|---|---|
| Appends the session tracking comment to production/session-state/active.md. | Missed | Passed |
| Points the session tracking comment log reference to docs/consistency-failures.md. | Missed | Passed |
The instructions your model reads when the skill loads.
!bash "${CLAUDE_SKILL_DIR}/../../hooks/yaml-helper.sh" resolve_config --keys automation,workflow,system_overrides
Detects cross-document inconsistencies by comparing all GDDs against the
entity registry (design/registry/entities.yaml). Uses a grep-first approach:
reads the registry once, then targets only the GDD sections that mention
registered names — no full document reads unless a conflict needs investigation.
This skill is the write-time safety net. It catches what /design-system's
per-section checks may have missed and what /review-all-gdds's holistic review
catches too late.
When to run:
/review-all-gdds (so that skill starts with a clean baseline)/create-architecture (inconsistencies poison downstream ADRs)/consistency-check entity:[name] to check one entity specificallyOutput: Conflict report + optional registry corrections
Every AskUserQuestion call follows .claude/docs/automation-modes.md
(collaborative asks always · guided major-only · autonomous logs and proceeds;
automation_always_ask categories always prompt).
workflow (see .claude/docs/workflow-modes.md), applied per GDD at its
effective tier — the system_overrides row for that GDD's system (its
filename stem) when the block lists one, else the project value:
full — full entity-registry cross-check against all GDD sections.standard — cross-check against the required sections only. The report's
Scope line says so, and each value stated for a registered name outside those
sections is listed as not checked at this tier (Phase 3 applies this).minimal — not meaningful (no GDDs to check).test cases passed, vs 4 / 20 without
More skills from the same source and nearby in the registry, with their headline benchmark lift.