| name | check-consistency |
| description | Validate that all skills and project conventions are structurally consistent by running the deterministic checker script. Use when the user says "check consistency", "verificar consistência", "validate skills" or "validar skills", and before committing any skill or config change. Runs scripts/check-consistency.mjs (frontmatter, sections, naming, hardcoded URLs, orphan refs, changelog coverage) rather than eyeballing the rules. |
| metadata | {"version":"2.0.0"} |
Check Consistency
Purpose
Validate that every skill in .claude/skills/ and the project's conventions hold, using a real
script so the result is deterministic (not a best-effort prose scan). Run before commits or after
any skill/config change.
Prerequisites
- Node.js available in PATH (the checker is
scripts/check-consistency.mjs)
.specs/config.md — source of truth for constants and the canonical Skill Format
Instructions
Step 1: Run the Checker
From the project root, run:
node scripts/check-consistency.mjs
The script validates, deterministically:
- Skill structure — each
.claude/skills/<name>/SKILL.md exists, has valid frontmatter
(name matching its folder, specific description), a verb-substantive name, and all 6 canonical
body sections.
- Hardcoded values — the repo URL literal must not appear outside
.specs/config.md.
- Orphaned references — no references to old flat skill paths (
.opencode/skills/*.md) or
renamed files (tdd-workflow, requirements-gathering).
- Changelog integrity — every archived spec ID appears in
CHANGELOG.md and vice-versa
(skipped when the archive is empty).
Step 2: Interpret the Result
- Exit code
0 → all checks passed.
- Exit code
1 → the script prints each FAIL <message> with the file path. Fix each one and
re-run until it exits 0.
Step 3: Fix and Re-run
For each violation, apply the suggested fix (move a flat file into a skill folder, add missing
frontmatter/section, replace a hardcoded URL with a .specs/config.md reference, etc.), then
re-run Step 1.
Output
Report the script's pass/fail summary. On failure, list each violation with its file path and the
fix applied. On success: All checks passed.
Examples
Example 1: All clean
User says: "verificar consistência"
Agent should: run node scripts/check-consistency.mjs → exit 0 → report "All checks passed".
Example 2: Violation found
User says: "check consistency"
Agent should: run the script → it reports a skill missing the ## Output section and a hardcoded
URL → fix both → re-run → exit 0 → report what was fixed.
References
scripts/check-consistency.mjs — the deterministic checker this skill runs.specs/config.md — constants and canonical Skill Format.claude/skills/create-skill/SKILL.md — how skills must be structured.specs/memory/component-catalog.md — reusable code inventory
