release
Create a new release by bumping version, committing, and pushing a git tag. Use when the user wants to release a new version (e.g., "release 1.0.1", "release patch", "make a release", "bump version and release", "create version 2.0.0").
When & Why to Use This Skill
This Claude skill automates the software release lifecycle by handling version increments, multi-file synchronization, and Git operations. It streamlines the deployment process by ensuring consistent versioning across configuration files (such as package.json and tauri.conf.json) and automatically triggering CI/CD pipelines through standardized Git tagging and pushing.
Use Cases
- Automating patch releases: Quickly increment version numbers and push tags for urgent bug fixes without manual file editing.
- Standardizing release cycles: Maintain a clean project history by using semantic versioning (major, minor, patch) through simple natural language commands.
- Cross-platform version synchronization: Automatically update version strings in multiple configuration files simultaneously to prevent build mismatches between web and desktop environments.
- CI/CD Pipeline Triggering: Seamlessly initiate automated GitHub Actions or build workflows by pushing authenticated release tags to the remote repository.
| name | release |
|---|---|
| description | Create a new release by bumping version, committing, and pushing a git tag. Use when the user wants to release a new version (e.g., "release 1.0.1", "release patch", "make a release", "bump version and release", "create version 2.0.0"). |
Release Workflow
Create a new release for Eyes on Claude Code.
Arguments
The user may specify a version in one of these formats:
- Explicit version:
1.0.1,2.0.0 - Semver bump:
patch,minor,major
If not specified, ask the user which version type they want.
Workflow
1. Determine New Version
If explicit version provided, use it directly.
If semver bump keyword provided:
# Get current version from package.json
node -p "require('./package.json').version"
Then calculate:
patch: 1.0.0 → 1.0.1minor: 1.0.0 → 1.1.0major: 1.0.0 → 2.0.0
2. Update Version in Files
Update version in both files:
package.json:
{
"version": "NEW_VERSION"
}
src-tauri/tauri.conf.json:
{
"version": "NEW_VERSION"
}
3. Commit Version Bump
git add package.json src-tauri/tauri.conf.json
git commit -m "Bump version to NEW_VERSION"
4. Create and Push Tag
git tag vNEW_VERSION
git push origin main vNEW_VERSION
5. Report Success
Output the following:
- New version number
- Git tag created
- GitHub Actions URL:
https://github.com/joe-re/claude-code-session-manager/actions - Remind user to check the draft release on GitHub after the build completes
Example User Requests
- "release 1.0.1"
- "release patch"
- "make a minor release"
- "bump version to 2.0.0 and release"
- "create a new release"
Notes
- Always ensure working directory is clean before running
- GitHub Actions will automatically build for all platforms (macOS, Linux, Windows)
- The release is created as a draft - user must publish it manually on GitHub