
Release
- 2 installs
- 2 repo stars
- Updated July 31, 2026
- avivsinai/shaon
release is a Claude Code skill that bumps versions, builds the binary, and creates a git tag to cut a new shaon release.
About
release is a Claude Code skill that cuts a new release of the shaon project. It bumps the version in Cargo.toml, the plugin.json, and README references, builds the release binary with cargo, runs clippy, shows the diff, commits, and creates an annotated git tag. A developer invokes it with /release and the new semver version when publishing a new shaon build. It reminds the user to git push --follow-tags when ready.
- 10-step release workflow for the shaon Rust project: bump, build, tag
- Bumps Cargo.toml, plugin.json, and README version references in sync
- Builds the release binary, runs clippy, commits, and creates an annotated git tag
Release by the numbers
- 2 all-time installs (skills.sh)
- Ranked #199 of 248 Release Management skills by installs in the Skillselion catalog
- Data as of Aug 1, 2026 (Skillselion catalog sync)
release capabilities & compatibility
- Capabilities
- release management · version bump · git tagging
- Works with
- github
- Use cases
- ci cd
- Runs
- Runs locally
- Pricing
- Free
What release says it does
Bump version, update all version references, build release binary, and create git tag. Use when cutting a new release of shaon.
**Tag**: Create an annotated git tag: `git tag -a v{VERSION} -m "Release v{VERSION}"`.
npx skills add https://github.com/avivsinai/shaon --skill releaseAdd your badge
Show developers this skill is listed on Skillselion. Paste this into your README.
| Installs | 2 |
|---|---|
| repo stars | ★ 2 |
| Last updated | July 31, 2026 |
| Repository | avivsinai/shaon ↗ |
What it does
Cutting a versioned release of the shaon Rust project with synced version bumps, build, and git tag.
Who is it for?
Cutting a new versioned release of the shaon Rust project with synchronized version bumps and a git tag.
Skip if: Any project other than shaon; it hardcodes Cargo.toml, plugin.json, and shaon paths.
When should I use this skill?
Cutting a new release of shaon with a new semver version number.
What you get
A single Release commit with all version references bumped, a clean build, and an annotated git tag.
- version-bumped commit
- annotated git tag
- release binary
By the numbers
- 10-step release workflow
Files
Release Workflow
Run this skill with: /release $ARGUMENTS
$ARGUMENTS should be the new version number (e.g., 0.4.0). If not provided, ask the user.
Steps
1. Validate version: Confirm $ARGUMENTS is a valid semver (MAJOR.MINOR.PATCH). Read current version from Cargo.toml.
2. Bump Cargo.toml: Update version = "..." in [package] section.
3. Bump plugin.json: Update "version": "..." in .claude-plugin/plugin.json.
4. Update README.md: Replace any occurrences of the old version string with the new version (e.g., in install commands, badges, or header).
5. Build release binary: Run cargo build --release and confirm it compiles cleanly.
6. Run clippy: Run cargo clippy -- -D warnings to ensure no lint issues.
7. Show diff: Run git diff and present the changes for review.
8. Commit: Create a single commit: Release v{VERSION} with the version-bumped files.
9. Tag: Create an annotated git tag: git tag -a v{VERSION} -m "Release v{VERSION}".
10. Report: Print the new version, tagged commit hash, and cached binary path (~/.cache/shaon/{VERSION}/shaon). Remind the user to git push --follow-tags when ready.
Related skills
FAQ
What files does the release skill bump?
Cargo.toml, .claude-plugin/plugin.json, and any version strings in README.md.
Does it push automatically?
No. It creates the commit and annotated tag, then reminds the user to run git push --follow-tags when ready.