Problem
Skills drift from standards over time, requiring periodic audits (like #23-26).
Proposal
Add a pre-commit hook that validates skill compliance:
Checks to enforce
Implementation
Could be a simple bash script or TypeScript validator in scripts/validate-skills.ts that runs on *.md changes in */skills/ directories.
Example output
❌ baselayer/skills/typescript-dev/SKILL.md
- description doesn't start with "This skill should be used when..."
- 523 lines (max 500)
✅ baselayer/skills/bun-dev/SKILL.md
Related
Prevents recurrence of issues like #23, #24, #25
Problem
Skills drift from standards over time, requiring periodic audits (like #23-26).
Proposal
Add a pre-commit hook that validates skill compliance:
Checks to enforce
name:in frontmatter matches directory name (kebab-case)description:starts with "This skill should be used when..."Implementation
Could be a simple bash script or TypeScript validator in
scripts/validate-skills.tsthat runs on*.mdchanges in*/skills/directories.Example output
Related
Prevents recurrence of issues like #23, #24, #25