Release
Generate changelog from commits, bump version, create GitHub release, publish to npm. Use when user wants to release, publish, or ship a new version.From its SKILL.md
npx -y skills add Houseofmvps/ultraship --skill releaseAssembled from the repository path, not quoted from the project. Check it against their README if it does not work.
SKILL.md
2.9 KB, as published. Nobody here has run it
Release
Full release pipeline: changelog → version bump → commit → tag → GitHub release → npm publish.
Process
Step 1: Determine Version Bump
Check recent commits since last tag to determine semver bump:
git describe --tags --abbrev=0 2>/dev/null || echo "none"
git log $(git describe --tags --abbrev=0 2>/dev/null || git rev-list --max-parents=0 HEAD)..HEAD --oneline
Analyze commit messages:
- Any
BREAKING CHANGE:or!:→ major bump - Any
feat:→ minor bump - Only
fix:,chore:,docs:,refactor:→ patch bump
If the user specifies a version (e.g., "release 2.0.0"), use that instead.
Step 2: Generate Changelog
Group commits by type:
## What's New
- feat: Add deploy command with pre-flight checks
- feat: Add content scoring with readability analysis
## Bug Fixes
- fix: Secret scanner false positive on .env.example
## Other Changes
- chore: Update dependencies
- refactor: Restructure SEO scanner for cross-page analysis
Step 3: Version Bump
Update version in:
package.json— theversionfield- Any other version references the project uses
# Read current version
node -e "console.log(JSON.parse(require('fs').readFileSync('package.json','utf8')).version)"
Use the Edit tool to update the version string.
Step 4: Commit & Tag
git add package.json CHANGELOG.md
git commit -m "release: v<new-version>"
git tag -a v<new-version> -m "v<new-version>"
Step 5: Push
git push origin main --tags
Step 6: GitHub Release
gh release create v<new-version> --title "v<new-version>" --notes "<changelog>"
Use the changelog from Step 2 as release notes.
Step 7: npm Publish (if applicable)
Only if package.json exists and has a name field (and is not private):
npm publish
If publish fails due to auth, show the user how to set up their npm token.
Step 8: Post-Release Summary
====================================
RELEASE COMPLETE
====================================
Package: ultraship
Version: 1.0.7
Tag: v1.0.7
Commits: 12 since last release
GitHub: https://github.com/Houseofmvps/ultraship/releases/tag/v1.0.7
npm: https://www.npmjs.com/package/ultraship
====================================
Changelog:
- 3 new features
- 2 bug fixes
- 1 breaking change
====================================
Key Principles
- Never skip the changelog — every release needs a clear description
- Always tag — tags are how users pin versions
- Atomic releases — version bump + changelog in one commit, then tag
- Respect user's git email — use configured git email for commits