Validate TheOneKit registry integrity across 20+ checks. Use for 'check kit health', 'something feels broken', 'validate before release', or after adding skills/agents.
Validates that all registry fragments, skills, and manifest are consistent and coherent.
/t1k:doctor # Read-only validation report
/t1k:doctor fix # Attempt to fix detected issues
Routing fragments:
!cat .claude/t1k-routing-*.json 2>/dev/null || echo "NO ROUTING FRAGMENTS FOUND"
Activation fragments:
!cat .claude/t1k-activation-*.json 2>/dev/null || echo "NO ACTIVATION FRAGMENTS FOUND"
Metadata:
!cat .claude/metadata.json 2>/dev/null || echo "NO METADATA FOUND"
Agent files:
!ls .claude/agents/*.md 2>/dev/null || echo "NO AGENTS"
Skill directories: !
ls -d .claude/skills/*/SKILL.md 2>/dev/null || echo "NO SKILLS"Run all checks in sequence. Full check list: references/checks.md
See references/frontmatter-recommendations.md for recommended values and output format.
fix mode)Only deterministic fixes: regenerate .t1k-manifest.json, detect orphaned/stale files, report what needs manual attention. Full details: references/fix-mode.md
## Doctor Report — {date}
### Checks
- Role coverage: [PASS | FAIL — missing agent for role X]
- Skill existence: [PASS | FAIL — missing skill: Y]
...
### Issues Found
- [issue description + file + line]
### Recommended Fixes
- [action]
origin, repository, module, protected manually. CI manages them. Check #16 validates consistency.modules/{name}/skills/ flattened to .claude/skills/ during release. The module: frontmatter preserves the original assignment.