| name | developer-workflow |
| description | Manage skill updates, patches, and versioning for the Family Doctor suite. Use when updating skills, creating new modules, managing changelog, or handling skill version changes. Triggers on "update skill", "add new module", "version change", "changelog". |
| allowed-tools | ["bash","glob","read"] |
| version | 1.0.0 |
Developer Workflow
Manage patches, versioning, and changelog for the Family Doctor skill suite.
When to Use
- Updating any skill file (SKILL.md)
- Adding a new skill module
- Managing version numbers
- Writing changelog entries
- Creating patch documentation
Version Numbering
Follow semantic versioning: MAJOR.MINOR.PATCH
- MAJOR: Breaking changes to routing or output contracts
- MINOR: New features, new skills, new capabilities
- PATCH: Bug fixes, documentation updates
How to Execute
Before Any Change
- Read current SKILL.md to understand the existing structure
- Read CHANGELOG.md (if exists)
- Identify the version number to update
After a Change
- Update version in SKILL.md frontmatter (
version: X.Y.Z)
- Add changelog entry to CHANGELOG.md
- Document what changed and why
Changelog Entry Format
## [X.Y.Z] - YYYY-MM-DD
### Added
- [Skill]: description of new feature
### Changed
- [Skill]: description of change
### Fixed
- [Skill]: description of fix
### Security
- [Skill]: security-related change
Skill File Structure
Each skill follows this pattern:
skill-name/
├── SKILL.md # Required: name, description, allowed-tools, instructions
├── references/ # Optional: reference docs
├── scripts/ # Optional: executable scripts
└── evals/ # Optional: test cases
SKILL.md Frontmatter
---
name: skill-name
description: One-line description. Triggers on keywords.
allowed-tools: [tool1, tool2]
---
Testing Checklist
Before committing changes:
Rollback
If a change causes problems:
- Revert SKILL.md to previous version
- Revert version number
- Do NOT retry the same change without understanding the failure
- Document the failure in CHANGELOG
Safety Rules
- No retry on failure: If patch fails, rollback and report
- Backup before change: Snapshot current state
- Atomic operations: All-or-nothing patch application
- Audit trail: Every change logged with timestamp