Claude-skill-registry consistency-enforcement
Documentation consistency enforcement - prevents drift between README.md and actual codebase state. Auto-activates when updating docs, committing changes, or working with skills/agents/commands.
git clone https://github.com/majiayu000/claude-skill-registry
T=$(mktemp -d) && git clone --depth=1 https://github.com/majiayu000/claude-skill-registry "$T" && mkdir -p ~/.claude/skills && cp -r "$T/skills/data/consistency-enforcement" ~/.claude/skills/majiayu000-claude-skill-registry-consistency-enforcement && rm -rf "$T"
skills/data/consistency-enforcement/SKILL.mdConsistency Enforcement Skill
Layer 4 Defense Against Documentation Drift
Auto-activates to maintain documentation consistency when working on docs, skills, agents, or commands.
See: workflow.md for step-by-step scenarios See: templates.md for checklists and commands
When This Activates
Keywords: "readme", "documentation", "docs", "commit", "sync", "update", "skill", "agent", "command", "count", "marketplace", "consistency", "drift"
Critical Consistency Rules
Rule 1: README.md is Source of Truth
All counts must match reality:
# Count actual resources ls -d plugins/autonomous-dev/skills/*/ | wc -l # Skills ls plugins/autonomous-dev/agents/*.md | wc -l # Agents ls plugins/autonomous-dev/commands/*.md | wc -l # Commands
Rule 2: All Docs Must Match README.md
These files MUST show the same counts:
(primary source)README.mddocs/SYNC-STATUS.mddocs/UPDATES.mdINSTALL_TEMPLATE.md
(metrics).claude-plugin/marketplace.json
Rule 3: Never Reference Non-Existent Skills
# Verify skill exists before referencing ls -1 plugins/autonomous-dev/skills/
Rule 4: marketplace.json Matches Reality
{ "metrics": { "agents": 8, "skills": 12, "commands": 21 } }
4-Layer Defense System
| Layer | Location | Purpose |
|---|---|---|
| 1 | | Automated CI/CD enforcement |
| 2 | | Agent memory checklist |
| 3 | | Pre-commit hook (optional) |
| 4 | This skill | Auto-reminder during work |
Run Tests
pytest tests/test_documentation_consistency.py -v
Quick Workflow
When adding/removing skills, agents, or commands:
- Update README.md count
- Update cross-reference files (SYNC-STATUS.md, UPDATES.md, etc.)
- Update marketplace.json metrics
- Run consistency tests
- Commit
See: workflow.md for detailed scenarios
Why This Matters
Documentation drift causes user confusion:
- README shows "9 Skills" but plugin has 12
- README mentions skill that doesn't exist
- User tries to use non-existent feature
With 4-layer defense:
- Layer 1: Tests fail in CI/CD
- Layer 2: doc-master catches before docs.json
- Layer 3: Pre-commit hook blocks commit
- Layer 4: This skill reminds during work
Result: Documentation always matches reality
Integration
Works with:
- documentation-guide: HOW to write docs
- git-workflow: HOW to commit changes
- project-management: PROJECT.md consistency
Related Files
- workflow.md - Step-by-step scenarios
- templates.md - Checklists and commands