-
Notifications
You must be signed in to change notification settings - Fork 2
Closed
Labels
component:skillSkills layerSkills layereffort:small< 1 hour< 1 hourenhancementNew feature or requestNew feature or requestgood first issueGood for newcomersGood for newcomerspriority:mediumShould be addressedShould be addressed
Description
Summary
The command-development skill lacks a scripts/ directory with utility scripts, unlike the hook-development skill which provides helpful validation tools (validate-hook-schema.sh, test-hook.sh, hook-linter.sh).
Current State
command-development/
├── SKILL.md
├── examples/
│ ├── plugin-commands.md
│ └── simple-commands.md
└── references/
└── (9 reference files)
Proposed Addition
command-development/
├── SKILL.md
├── examples/
├── references/
└── scripts/
├── validate-command.sh # Validate command file structure
└── check-frontmatter.sh # Validate YAML frontmatter
Context
The references/testing-strategies.md file already includes inline script examples for command validation:
- YAML frontmatter validation
- File structure validation
- Frontmatter field validation
These could be extracted into actual executable scripts for users to run directly.
Benefits
- Users can validate commands before deployment
- Consistent with hook-development skill pattern
- Scripts are token-efficient (can be executed without loading into context)
- Improves developer experience
Acceptance Criteria
- Create
scripts/directory - Add
validate-command.sh- validates command file structure - Add
check-frontmatter.sh- validates YAML frontmatter fields - Scripts should be executable (
chmod +x) - Update SKILL.md to reference new scripts in "Additional Resources" section
Reactions are currently unavailable
Metadata
Metadata
Assignees
Labels
component:skillSkills layerSkills layereffort:small< 1 hour< 1 hourenhancementNew feature or requestNew feature or requestgood first issueGood for newcomersGood for newcomerspriority:mediumShould be addressedShould be addressed