bump-version
Skill1 starsChanged 6 months agoMITView on GitHub
同步 bump workspace 版本号三处(Cargo.toml / src-tauri/Cargo.toml / src-tauri/tauri.conf.json)→ 跑 `just release-check`(版本一致 + preflight + lock 同步)。**只在**用户显式 `/bump-version <new>` 或自然语言"bump 版本 / 升版本号 / bump 到 X.Y.Z / 发 vX"时触发——模型不能自主调用,因为这是发版动作必须用户授权。完整发版流程见 `release-runbook` skill。
- Commits and pushes
43 other projects use a version of this.
Adopted by
Most recently taken up by
- lorem-dev/duologtheir own version, first seen Nov 15, 2026
- nesnilnehc/ai-cortextheir own version, first seen Nov 8, 2026
- OldemarJesus/connectlife-mcp-servertheir own version, first seen Nov 8, 2026
- humanlayer/humanlayertheir own version, first seen Oct 25, 2026
- asta-nguyen/kamehadbtheir own version, first seen Oct 16, 2026
- kostiantyn-matsebora/canopy-examplestheir own version, first seen Oct 11, 2026
Used with
Projects with it also use oss-pr, pr-automation and 7 more.
Other files people use alongside this one.
Files found in the same public projects as a version of this one, more often than they turn up anywhere else. Each project counts once, large collections count for less, and this file's own repository is left out.
CES-LtdSkilloss-pr
Use when creating a pull request, after committing changes, or when user invokes /oss-pr. Covers branch management, quality checks, commit, push, and PR creation.
Also in 3 projects that use this
CES-LtdSkillpr-automation
PR Automation Orchestrator: poll open PRs, check CI, run review, fix, and merge eligible PRs. Use when: (1) Invoked by daemon via scripts/pr-automation.sh, (2) User says "/pr-automation".
Also in 3 projects that use this
volovelySkillpr-fix
This skill should be used when the user asks to "fix PR comments", "address PR feedback", "resolve PR comments", provides a GitHub PR URL with intent to fix, or says "pr-fix". It reads all review comments on a PR, decides which need code fixes vs. replies, makes the fixes, and posts replies — all with explicit user approval before any GitHub action.
Also in 3 projects that use this
lbednerSkilli18n
Use when a code or template change introduces a new translation message key, in either the framework CLI (aegis/i18n/locales/) or a generated project's CLI (the app/i18n/locales/ template tree). Covers adding the real English string, stubbing the same key into every other locale for parity, and the separate translation PR that later replaces placeholders with reviewed native text.
Also in 4 projects that use this
AnthropicSkillarchitecture
Create or evaluate an architecture decision record (ADR). Use when choosing between technologies (e.g., Kafka vs SQS), documenting a design decision with trade-offs and consequences, reviewing a system design proposal, or designing a new component from requirements and constraints.
Also in 4 projects that use this
NVIDIASkilltesting
Run Python and Rust tests for physicsnemo-curator using uv + pytest with coverage reporting via pytest-cov, and cargo-nextest for Rust tests. Includes benchmark workflows with pytest-benchmark and criterion.
Also in 5 projects that use this
- +2 more from CES-Ltd
Other versions43 projects use a version of this.
Word for word · 0
None found.
Edited · 0
None found.
Wrote their own version · 43
- iOfficeAI/AionUi★ 34ksame name
- Skyvern-AI/skyvern★ 23ksame name
- humanlayer/humanlayer★ 13ksame name
- modelcontextprotocol/csharp-sdk★ 4.6ksame name
- cuthbertLab/music21★ 2.6ksame name
- wandb/weave★ 1.1ksame name
- wesbos/JSON-Alexander★ 944same name
- opentabs-dev/opentabs★ 926same name
- ai-dynamo/aiperf★ 858same name
- termio-sh/termio★ 790same name
33 more not listed
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 repository31 other files it gives its agents.
- AGENTS.mdAGENTS.md
- CLAUDE.mdCLAUDE.md
- crates/CLAUDE.mdCLAUDE.md
- openspec/CLAUDE.mdCLAUDE.md
- src-tauri/CLAUDE.mdCLAUDE.md
- ui/CLAUDE.mdCLAUDE.md
- bug-huntSkill
- debug-firstSkill
- dep-updateSkill
- e2e-http-verifySkill
- insta-reviewSkill
- mark-tasks-doneSkill
- openspec-apply-changeSkill
- openspec-archive-changeSkill
- openspec-bulk-archive-changeSkill
- openspec-continue-changeSkill
- openspec-exploreSkill
- openspec-ff-changeSkill
- openspec-new-changeSkill
- openspec-onboardSkill
- openspec-proposeSkill
- openspec-sync-specsSkill
- openspec-verify-changeSkill
- perfSkill
- port-dashboardSkill
- preflightSkill
- refactorSkill
- release-runbookSkill
- ts-parity-checkSkill
- ts-ui-compareSkill
- wait-ciSkill
The file
Files
bump-version
触发:用户显式 /bump-version <new-version> 或自然语言"bump 到 0.1.2 / 升版本 / 准备发 vX.Y.Z"。
不触发:任何没有明确版本号的场景。模型自主调用已禁用(disable-model-invocation: true)—— bump 版本是有副作用的发版动作,必须用户授权。
输入
- 新版本号(SemVer,形如
0.1.1/1.2.3)
约束:
- 必须是纯数字
X.Y.Z——禁止0.3.0-rc.1/0.3.0-beta等含字母后缀(CLAUDE.md "发布与分支策略"段:Windows MSI bundler 不接受 pre-release 含字母) - 若用户没给版本号:用 AskUserQuestion 问一次,不要自己猜
三处同步点(必须一致,否则 just release-check 拒)
Cargo.tomlworkspace 根:[workspace.package]下version = "X.Y.Z"src-tauri/Cargo.toml独立 manifest:[package]下version = "X.Y.Z"src-tauri/tauri.conf.jsonJSON:"version": "X.Y.Z"
工作步骤
1. 读取当前版本
grep -E '^version\s*=' Cargo.toml | head -1 | sed -E 's/.*"([^"]+)".*/\1/'
grep -E '^version\s*=' src-tauri/Cargo.toml | head -1 | sed -E 's/.*"([^"]+)".*/\1/'
grep -E '"version":' src-tauri/tauri.conf.json | head -1 | sed -E 's/.*"version":[[:space:]]*"([^"]+)".*/\1/'三处应当相等(just release-check 的前置不变量)。若不一致:停下来报告当前状态、让用户决策以谁为基准,再统一——不要强行 bump,可能覆盖别人未 push 的改动。
2. 用 Edit 工具改三处
禁止用 sed -i(BSD/macOS 需要空串参数,易出错;Edit 工具有 stale-read 保护)。
Cargo.toml的[workspace.package]段里version = "<old>"→version = "<new>"src-tauri/Cargo.toml的顶层[package]段里version = "<old>"→version = "<new>"src-tauri/tauri.conf.json的"version": "<old>",→"version": "<new>",
3. 跑 just release-check
just release-check该命令检查三处版本一致 + 工作树干净 + 跑 just preflight(fmt + lint + test + spec-validate)。
预期:工作树检查会失败——因为刚改了三处。这是设计:just release-check 是"commit 前最后一步",假设此时工作树已经干净。本 skill 的预期是"先 bump 再 commit",所以跳过工作树干净检查,直接跑 preflight 等效命令验证:
cargo fmt --all -- --check
cargo clippy --workspace --all-targets -- -D warnings
cargo test --workspace
openspec validate --all --strict四项全绿即可。
注意:just release-check / cargo check 会把 Cargo.lock + src-tauri/Cargo.lock 改掉(因为 workspace 版本变了)——这两个 lock 文件也属于本次 bump 的产物,commit 时必须一起 add(见 release-runbook F5)。
4. 报告给用户
输出:
- 三处版本号的新值(grep 再确认一次)
- preflight 四项结果
- lock 文件是否被 cargo 重写(
git status看Cargo.lock/src-tauri/Cargo.lock是否进 staged 区) - 下一步手动动作(不自动跑):
git add Cargo.toml Cargo.lock src-tauri/Cargo.toml src-tauri/Cargo.lock src-tauri/tauri.conf.jsongit commit -m "chore(release): vX.Y.Z"- push + 开 PR → merge → 在 main 上
git tag vX.Y.Z && git push origin vX.Y.Z
不自动 commit / 不自动打 tag——发版动作必须用户手动收尾。
硬性约束
- 不写注释、不动业务代码——只改三处版本字符串 + 触发 cargo 重生 lock
- 若用户传入的
<new>不是合法 SemVer 纯数字(如v0.1.1、0.1缺 patch、0.3.0-rc.1含字母):拒绝并让用户重输 - 若三处当前版本不一致:不要强行 bump,先让用户确认基准
- 完整发版流水线(push → wait-ci → merge → tag → 监控 release.yml → publish)走
release-runbookskill,本 skill 只管"改三处 + verify"
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.

