Release
Skill kouko/monkey-knowledge-youtube-skills/.claude/skills/release
Use when publishing a new version — bumps versions across all config files, updates CHANGELOG, verifies utility sync, commits, creates PR, and tags releaseFrom its SKILL.md
npx -y skills add kouko/monkey-knowledge-youtube-skills --skill releaseAssembled from the repository path, not quoted from the project. Check it against their README if it does not work.
One thing to look at
- 2 stars2 stars. Stars are a popularity signal and not a quality one, but at this level it is likely that nobody has read this closely except its author, and you would be relying on your own review.
SKILL.md
2.3 KB, as published. Nobody here has run it
Release New Version
Quick Start
/project:release <version>
| Parameter | Description |
|---|---|
version | Target version (e.g. 1.2.0). Determines SemVer bump level |
How it Works
1. Determine Version Bump
Analyze commits since last release (git log <last-tag>..HEAD) and apply:
| Commit Type | Bump | Example |
|---|---|---|
| feat | Minor | 1.0.0 → 1.1.0 |
| refactor | Minor | 1.1.0 → 1.2.0 |
| fix / internal | Patch | 1.0.0 → 1.0.1 |
| breaking change | Major | 1.0.0 → 2.0.0 |
2. Bump Skill Versions
Update metadata.version in each skills/*/SKILL.md:
- Skills with functional changes: Minor or Patch based on scope
- Skills with only
_utility__changes: Patch bump
3. Bump Plugin Version
Update version in all 3 files (must be identical):
| File | Fields |
|---|---|
.claude-plugin/plugin.json | version |
.claude-plugin/marketplace.json | metadata.version + plugins[0].version |
gemini-extension.json | version |
4. Update CHANGELOG.md
Insert new section before the previous version entry. Format: Keep a Changelog
Sections: Added / Changed / Fixed / Internal
Append comparison link at bottom:
[X.Y.Z]: https://github.com/kouko/monkey-knowledge-youtube-skills/compare/vPREV...vX.Y.Z
5. Verify
Run bash scripts/verify-utility-sync.sh — all _utility__ copies must be identical.
6. Commit & PR
- Commit:
chore: bump version to X.Y.Z - Push branch → Create PR → Merge
7. Tag & GitHub Release
After PR merge, on main:
git tag vX.Y.Z
git push origin vX.Y.Z
gh release create vX.Y.Z --title "vX.Y.Z" --notes "<CHANGELOG content for this version>"
Checklist
- All
skills/*/SKILL.mdversions bumped - 3 plugin/extension configs have identical version
- CHANGELOG.md has new version section + comparison link
-
verify-utility-sync.shpasses - Commit message follows
chore: bump version to X.Y.Z - PR created and merged
- Tag pushed
- GitHub Release created (with release notes from CHANGELOG)