release-skill
Bump version, update changelog, commit, tag, push, and build release installer
When & Why to Use This Skill
This Claude skill automates the end-to-end software release workflow, handling version bumping, changelog management, and deployment tasks. It streamlines the transition from development to production by synchronizing versioning across multiple configuration files (NPM and Rust/Tauri), executing build scripts, and managing Git repository tags and pushes, ensuring a consistent and error-free release process.
Use Cases
- Automating version increments (patch, minor, major) across package.json, Cargo.toml, and tauri.conf.json to maintain project consistency.
- Streamlining the documentation process by automatically migrating 'Unreleased' changes to dated version sections in CHANGELOG.md.
- Reducing manual errors in the release cycle by verifying builds locally before committing code and pushing tags to remote repositories.
- Standardizing the distribution of desktop applications by providing direct paths to generated installers (like NSIS) after a successful build.
| name | release-skill |
|---|---|
| description | Bump version, update changelog, commit, tag, push, and build release installer |
Release Workflow
When the user says "release", "/release", or "push, release", execute this workflow.
1. Determine Version
Check current version in package.json. Ask user for bump type if not specified:
- patch: 0.1.0 → 0.1.1 (bug fixes)
- minor: 0.1.0 → 0.2.0 (new features)
- major: 0.1.0 → 1.0.0 (breaking changes)
2. Update Version in All Files
Update version string in these three files:
package.json- field"version": "X.Y.Z"src-tauri/Cargo.toml- fieldversion = "X.Y.Z"src-tauri/tauri.conf.json- field"version": "X.Y.Z"
3. Update CHANGELOG.md
- Move all content under
## [Unreleased]to a new version section - Add today's date in format
## [X.Y.Z] - YYYY-MM-DD - Leave empty
## [Unreleased]section at top
Example:
## [Unreleased]
## [0.2.0] - 2025-12-29
### Pridane
- New feature...
4. Build Release
Build BEFORE committing to verify everything works:
npm run tauri build
If build fails, fix issues and retry. Don't proceed until build succeeds.
5. Commit, Tag, and Push
Only after successful build:
git add -A
git commit -m "chore: release vX.Y.Z"
git tag vX.Y.Z
git push && git push --tags
6. Report Results
Show the path to the built installer:
- NSIS installer:
src-tauri/target/release/bundle/nsis/Kniha Jázd_X.Y.Z_x64-setup.exe
Notes
- Cargo.lock will auto-update - include it in the commit
- CHANGELOG is in Slovak (Pridane, Zmenene, Opravene)