semver-release
Skill1 starsChanged 50 days agoMITView on GitHub
Cut a SemVer release driven by Conventional Commits since the last tag. Bumps the version in detected manifest files (package.json, pyproject.toml, Cargo.toml, .claude-plugin/plugin.json, …), updates CHANGELOG.md in Keep a Changelog format, commits, tags, pushes, and optionally creates a GitHub release. Use when the user says "/semver-release", "cut a release", "tag a new version", "vydej release", "udělej release", or asks to ship a new version.
- Commits and pushes
1 other project uses a version of this.
Adopted by
Most recently taken up by
- radiovisual/claude-skillstheir own version, first seen Nov 16, 2026
Other versions1 project uses a version of this.
Word for word · 0
None found.
Edited · 0
None found.
Wrote their own version · 1
- radiovisual/claude-skills★ 0same name
How matches are found. Word for word: the exact same text. Edited: shares passages with this file (“99% same” means 99% of its five-word phrases also appear here; 10% or more counts). Their own version: similar meaning, or, weakest, the same name. We can’t tell which project had it first. Projects are counted among the 200 most-starred candidates, and mentions are links to the repository we found, up to 50 per site, so both counts are a floor.
In this repository50 other files it gives its agents.
- AGENTS.mdAGENTS.md
- anonymize-outputSkill
- cart-fillSkill
- client-questionsSkill
- code-reviewSkill
- conventional-commitSkill
- critical-pathSkill
- debate-replySkill
- decision-analysisSkill
- dependency-diagramsSkill
- dm-catchupSkill
- dm-composeSkill
- dockerizeSkill
- epic-breakdownSkill
- geo-page-auditSkill
- init-projectSkill
- kodexSkill
- launchpad-fixSkill
- mail-catchupSkill
- mcp-server-adoptSkill
- merge-prSkill
- mikrotik-auditSkill
- oponenturaSkill
- pr-rebase-sweepSkill
- raw-source-checkSkill
- resource-busySkill
- retroSkill
- second-opinionSkill
- session-recallSkill
- skill-dry-runSkill
- skillifySkill
- skillset-adoptSkill
- task-deliverySkill
- task-estimateSkill
- teammate-checkSkill
- team-standupSkill
- token-auditSkill
- tracker-backfillSkill
- tracker-log-entrySkill
- tracker-setup-trackerSkill
- tracker-startSkill
- tracker-stopSkill
- wireguard-diagnoseSkill
- work-endSkill
- work-reconcileSkill
- work-setupSkill
- work-standupSkill
- work-startSkill
- work-statusSkill
- worktree-cleanupSkill
The file
Show its rules and text
We split this skill into the rules it gives an agent
17 rules. About 0 are common, 10 are distinctive, and 7 are very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈10
Distinctive · estimate
This author's own choices. Worth a look.
7
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Distinctive: line 11
Follow these steps in order.
- Distinctive: line 33
If no tag exists yet (first release), use the full git log since the initial commit.
- Distinctive: line 35
If there are no commits since the last tag, stop and tell the user there's nothing to release.
- Distinctive: line 39
Search the repo root for a manifest with a version field, in this priority order (first hit wins for "current version".
- Very specific: line 53
If none are found, ask the user for the current version (or assume 0.0.0 if it's a first release).
- Distinctive: line 96
If the user picks a custom version, validate it as SemVer before continuing.
- Very specific: line 124
Use today's date in YYYY-MM-DD form.
- Very specific: line 126
If CHANGELOG.md already exists, splice the new entry between the header (and any "Unreleased" section) and the previous most recent entry.
- Very specific: line 128
If CHANGELOG.md doesn't exist, ask the user whether to create it.
- Distinctive: line 156
After the edits, run git diff --stat to show what changed.
- Distinctive: line 160
Before tagging, check whether CI on the current commit is green:
- Very specific: line 177
If gh run list fails (no GitHub remote, no gh auth, no workflows) — skip the CI check silently.
- Distinctive: line 192
Ask the user to choose:
- Very specific: line 213
Never use --no-verify. If a hook fails, stop, show the user the hook output, suggest a fix, and let them decide.
- Distinctive: line 217
Ask the user to choose (default yes):
- Very specific: line 242
If the version is a prerelease (contains -alpha, -beta, -rc, etc.), pass --prerelease.
- Distinctive: line 249
Commit SHA and tag
≈ “Common” is an estimate: at least 1 in 5 of the 364,980 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Files
semver-release — procedure
Cut a SemVer release from Conventional Commits. Every interactive choice is put to the user as an explicit set of options so they can override. Never bypass hooks (--no-verify); never force-push.
Follow these steps in order.
1. Pre-flight
- Working tree must be clean:
git status --porcelainshould be empty. If not, stop and tell the user to commit or stash first. - Capture the current branch:
git branch --show-current. - Find the latest tag:
git describe --tags --abbrev=0 2>/dev/null(may fail if no tags exist — that's fine, this will be the first release). - Capture the tag format: did the last tag use a
vprefix (v1.2.3) or not (1.2.3)? Match that format. If no prior tags, default tovprefix.
2. Read commits since the last tag
git log <last-tag>..HEAD --pretty=format:'%H%x09%s%x09%b%x1e'(%x1e is record-separator; split on that.)
Parse each commit:
- Subject matches
^(?<type>feat|fix|docs|style|refactor|perf|test|build|ci|chore|revert)(?:\((?<scope>[^)]+)\))?(?<bang>!)?: (?<subject>.+)$. - Breaking change is signalled by either
!in the subject (e.g.feat!:) or aBREAKING CHANGE: <desc>footer in the body. - Commits that don't match the Conventional Commits pattern are classified as
other— count them but don't drive bump decisions off them.
If no tag exists yet (first release), use the full git log since the initial commit.
If there are no commits since the last tag, stop and tell the user there's nothing to release.
3. Read the current version
Search the repo root for a manifest with a version field, in this priority order (first hit wins for "current version"; you'll write back to all detected files in step 6):
| File | How to read |
package.json | .version (JSON) |
pyproject.toml | [project].version or [tool.poetry].version (TOML) |
Cargo.toml | [package].version (TOML) |
composer.json | .version (JSON, optional — often missing) |
.claude-plugin/plugin.json | .version (JSON) — for Claude Code plugins |
pubspec.yaml | version: (YAML) |
mix.exs | @version attribute |
*.csproj | <Version> element |
VERSION (plain file) | the trimmed contents |
If none are found, ask the user for the current version (or assume 0.0.0 if it's a first release).
Validate the version against SemVer (MAJOR.MINOR.PATCH, optional -prerelease and +build). If it doesn't parse, ask the user to confirm or correct.
4. Propose a version bump
Decision tree:
- If current version ≥ 1.0.0:
- Any commit with breaking change → major
- Else any
feat→ minor - Else any
fix/perf/refactor→ patch - Else (only
chore/docs/test/build/ci/style) → patch (and warn the user — usually you don't release pure infra commits)
- If current version < 1.0.0 (pre-1.0):
- Pre-1.0 SemVer is ambiguous; ask the user to choose:
- Option 1:
Treat feat as minor, BREAKING as major (post-1.0 rules)— recommended for projects close to 1.0 - Option 2:
Treat feat as patch, BREAKING as minor (stay in 0.x experimental)— recommended for early-stage - Option 3:
Custom — let me pick the bump kind directly
- Option 1:
- Apply the chosen rule to decide the bump kind.
- Pre-1.0 SemVer is ambiguous; ask the user to choose:
Compute the proposed version and show the user a summary:
Current: 0.5.3
Proposed: 0.6.0 (minor)
Reason: 3 feat commits since v0.5.3
- feat(auth): add OAuth login (abc1234)
- feat: support custom themes (def5678)
- feat(api): expose /metrics endpoint (1a2b3c4)
(also: 2 fix, 1 chore — see CHANGELOG entry below)Then ask the user to choose:
Accept proposed version (X.Y.Z)(recommended)Bump differently — major(offer the major version)Bump differently — minor(offer the minor version)Bump differently — patch(offer the patch version)Custom version— drop out to let user type the exact stringCancel
If the user picks a custom version, validate it as SemVer before continuing.
5. Generate the CHANGELOG entry
Format: Keep a Changelog 1.1.0.
Section mapping:
feat→ Addedfix→ Fixedperf,refactor(user-visible) → Changed- Breaking changes → Changed with a
**BREAKING:**prefix on the bullet (or a separate Removed/Changed entry if the change is purely removal) - Skip
chore,docs,style,test,build,ci,revertfrom the changelog (they're noise for users) — but noterevertif it reverts a feature shipped in a prior release.
Entry template:
## [X.Y.Z] - YYYY-MM-DD
### Added
- <subject from feat commit> ([<short-sha>](https://github.com/<owner>/<repo>/commit/<sha>))
### Changed
- <subject from refactor/perf>
### Fixed
- <subject from fix commit>Use today's date in YYYY-MM-DD form.
If CHANGELOG.md already exists, splice the new entry between the header (and any "Unreleased" section) and the previous most recent entry. Don't overwrite anything else.
If CHANGELOG.md doesn't exist, ask the user whether to create it. If yes, scaffold it with:
# Changelog
All notable changes to this project are documented in this file.
The format is based on [Keep a Changelog](https://keepachangelog.com/en/1.1.0/),
and this project adheres to [Semantic Versioning](https://semver.org/spec/v2.0.0.html).
<new entry goes here>6. Update version in manifest files
For every file detected in step 3, update the version string. Use precise Edit calls — don't rewrite the whole file.
Examples of exact patterns to match:
package.json:"version": "<old>"→"version": "<new>"pyproject.toml:version = "<old>"(inside[project]or[tool.poetry]) →version = "<new>"Cargo.toml:version = "<old>"(inside[package]) →version = "<new>".claude-plugin/plugin.json:"version": "<old>"→"version": "<new>"
Show the user the list of files about to be updated and ask them to choose:
Update all detected files(recommended)Pick a subset— list each file as a yes/noCancel
After the edits, run git diff --stat to show what changed.
7. Check CI for the head commit
Before tagging, check whether CI on the current commit is green:
gh run list --branch <branch> --limit 5 --json headSha,status,conclusion,workflowNameFilter to runs whose headSha matches git rev-parse HEAD. Classify:
- All
conclusion: success→ green, continue. - Any
status: in_progressorqueued→ pending, warn the user and ask them to choose:Wait for CI to finish, then re-run /semver-release(recommended)Release anyway — I know what I'm doingCancel
- Any
conclusion: failure/cancelled/timed_out→ failing, warn the user more strongly:Cancel and fix CI first(recommended)Release anyway — I have a justificationCancel
If gh run list fails (no GitHub remote, no gh auth, no workflows) — skip the CI check silently.
8. Final confirmation
Show the user a summary of what's about to happen:
About to:
• Update version in <files…> to X.Y.Z
• Append entry to CHANGELOG.md
• Commit: "chore(release): vX.Y.Z"
• Tag: vX.Y.Z (annotated)
• Push commit + tag to origin/<branch>Ask the user to choose:
Do it(recommended)Stop after commit — I'll tag/push manuallyCancel
9. Commit + tag
Stage only the version files and CHANGELOG.md (not everything). Then commit:
git commit -m "chore(release): vX.Y.Z"(Match the tag format you captured in step 1 — drop the v prefix in the message if the project doesn't use it.)
Annotated tag with the changelog entry as the message:
git tag -a vX.Y.Z -m "<one-line release summary>"Never use --no-verify. If a hook fails, stop, show the user the hook output, suggest a fix, and let them decide.
10. Push
Ask the user to choose (default yes):
Push commit and tag to origin/<branch>(recommended)Don't push — I'll do it myself
If yes:
git push origin <branch> && git push origin vX.Y.Z11. GitHub release
Ask the user to choose:
Create a GitHub release with the changelog entry as notes(recommended)Skip — just leave the tag
If yes:
gh release create vX.Y.Z --title "vX.Y.Z" --notes "$(cat <<'EOF'
<changelog entry body — without the H2 header line>
EOF
)"If the version is a prerelease (contains -alpha, -beta, -rc, etc.), pass --prerelease.
12. Final summary
Tell the user:
- The new version and tag
- Files updated
- Commit SHA and tag
- GitHub release URL (if created), or "tag pushed, no GitHub release"
- Reminder to bump the dev branch back to the next
-devversion if their workflow needs that (don't do it automatically — surface it as a follow-up).
Does it work?
Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.
No reviews yet
People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.
- It worked
- Partly
- It didn't
Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.
Your trail
Files you open will collect here, so you can find them again.
Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.
Now do this for your own.
Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.

