release-version
Skill7 starsChanged 5 months agoMITView on GitHub
Prepare a Prot Skills release branch — determine the next version, bump metadata, write release notes. Use when asked to "prepare a release", "bump version", "写release notes", "准备发版", "version bump", or when planning a new version before publishing.
10 other projects use a version of this.
Adopted by
Most recently taken up by
- kubetail-org/kubetailtheir own version, first seen Nov 16, 2026
- Nucs/Agentmastertheir own version, first seen Nov 13, 2026
- foldkit/foldkittheir own version, first seen Nov 2, 2026
- ngthluu/my-dev-skillstheir own version, first seen Nov 1, 2026
- cachewraith/cachewraith-skillstheir own version, first seen Oct 25, 2026
- crux-cli/cruxtheir own version, first seen Oct 13, 2026
Other versions10 projects use a version of this.
Word for word · 0
None found.
Edited · 0
None found.
Wrote their own version · 10
- kubetail-org/kubetail★ 1.8ksame name
- foldkit/foldkit★ 1.1ksame name
- corvo007/Gemini-Subtitle-Pro★ 835same name
- corvo007/MioSub★ 835same name
- Byte-n/larkDocx2md★ 34same name
- Vochsel/dump.page★ 3same name
- ngthluu/my-dev-skills★ 2same name
- Nucs/Agentmaster★ 1same name
- cachewraith/cachewraith-skills★ 0same name
- crux-cli/crux★ 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 repository7 other files it gives its agents.
- AGENTS.mdAGENTS.md
- CLAUDE.mdCLAUDE.md
- release-publishSkill
- release-tagSkill
- self-checkSkill
- submit-prSkill
- sync-agent-skillsSkill
The file
We split this skill into the rules it gives an agent
11 rules. 0 are common, 6 are distinctive, and 5 are very specific to this project.
0
Common
Most of the 9 edited versions we read keep these.
6
Distinctive
This author's own choices. Worth a look.
5
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- could be automatic: a setting could enforce it
- Very specific: line 17
Do not use for the PR merge and tag-push flow — that is /release-publish.
- Very specific: line 32
Read the current version from package.json.
- Very specific: line 41
Check whether docs/releases/v{NEXT_VERSION}.md already exists.
- Distinctive: line 42
If it exists, note this and skip release notes writing in Phase 2.
- Distinctive: line 43
If not, gather commits since the last release tag to draft notes.
- Distinctive: line 56
If there are no tags yet, fall back to git log --oneline to show all commits.
- Distinctive: line 64
Create and switch to the release branch:
- Distinctive: line 100
Commit the release notes:
- Distinctive: line 113
Run a local build check:
- Very specific: line 146
pnpm release:versionfails: ensure cargo is available and src-tauri/Cargo.toml is valid - Very specific: line 147
Version already exists: check git tag --list v{VERSION} — pick a different level or version
“Common” is measured: kept by at least 6 in 10 of the 9 edited versions of this file we could read. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Files
Release Version
Prepares a release branch with a version bump and release notes. Ends with a clean branch ready for release-publish or /submit-pr.
When to Use
- Choosing the next version level (
patch/minor/major) - Bumping version metadata across
package.json,tauri.conf.json,Cargo.toml,Cargo.lock - Writing or updating release notes from commits since the last tag
- Creating the
chore/release-v{X.Y.Z}branch
Do not use for the PR merge and tag-push flow — that is /release-publish.
Prerequisites
- Clean
mainbranch with no uncommitted changes pnpmandcargoavailable
Workflow
Execute these phases in order. Report the output of each phase before moving on.
Phase 1 — Determine Version
- Read the current version from
package.json. - Show the user the current version and ask which bump level to use:
patch— bug fixes, CI fixes (e.g. 0.0.4 → 0.0.5)minor— new features, backward compatible (e.g. 0.0.4 → 0.1.0)major— breaking changes (e.g. 0.0.4 → 1.0.0)
- Compute the next version string (e.g.
0.0.5). Check whether
docs/releases/v{NEXT_VERSION}.mdalready exists.- If it exists, note this and skip release notes writing in Phase 2.
- If not, gather commits since the last release tag to draft notes.
To gather commits:
LAST_TAG=$(git describe --tags --abbrev=0 2>/dev/null || echo "") if [[ -n "$LAST_TAG" ]]; then git log "$LAST_TAG..HEAD" --oneline else git log --oneline fiIf there are no tags yet, fall back to
git log --onelineto show all commits.
Output: confirmed next version and whether release notes need to be written.
Phase 2 — Create Release Branch and Bump Version
Create and switch to the release branch:
git checkout -b chore/release-v{NEXT_VERSION} mainBump the version:
pnpm release:version {LEVEL}This updates
package.json,src-tauri/tauri.conf.json,src-tauri/Cargo.toml,src-tauri/Cargo.lockand commitschore(release): bump version to {NEXT_VERSION}.
Output: release branch created with version bump committed.
Phase 3 — Write Release Notes
Skip this phase if docs/releases/v{NEXT_VERSION}.md already exists.
Copy the template:
cp docs/releases/TEMPLATE.md docs/releases/v{NEXT_VERSION}.md- Fill in the sections using the gathered commits, grouping by type:
- Highlights: the most impactful changes
- Added: new user-facing capabilities
- Changed: existing behavior that now works differently
- Fixed: bug fixes with visible impact
- Show the draft to the user for review before saving.
Commit the release notes:
git add docs/releases/v{NEXT_VERSION}.md git commit -m "docs(release): add v{NEXT_VERSION} release notes"
Output: release notes committed.
Phase 4 — Verify and Report
Run a local build check:
pnpm buildShow the final branch state:
git log main..HEAD --onelineReport to the user:
Release branch
chore/release-v{NEXT_VERSION}is ready. Version bumped to {NEXT_VERSION} with release notes.Next step: run
/release-publishto push, create PR, and trigger CI.
Output: verified release branch ready for publishing.
Quick Reference
| Step | Command |
| Bump version | pnpm release:version patch|minor|major |
| Gather commits | git log $(git describe --tags --abbrev=0)..HEAD --oneline |
| Check build | pnpm build |
Error Handling
pnpm release:versionfails: ensurecargois available andsrc-tauri/Cargo.tomlis valid- Version already exists: check
git tag --list v{VERSION}— pick a different level or version - Build fails after bump: fix the issue on the release branch before proceeding
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.

