bump-version
Skill4 starsChanged 16 days agoApache-2.0View on GitHub
Use when the user asks to bump, set or raise the duolog version, or to prepare a release commit. Do not use to only check the version; check-version does that. Do not use to create a tag or publish a release.
43 other projects use a version of this.
Adopted by
Most recently taken up by
- 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
- snowzhaozhj/claude-devtools-rstheir own version, first seen Oct 9, 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 repository10 other files it gives its agents.
- AGENTS.mdAGENTS.md
- CLAUDE.mdCLAUDE.md
- check-changesSkill
- check-versionSkill
- crit-cliSkill
- critSkill
- crit-storySkill
- bump-versionSkill
- check-changesSkill
- check-versionSkill
The file
We split this skill into the rules it gives an agent
9 rules. 0 are common, 5 are distinctive, and 4 are very specific to this project.
0
Common
Most of the 40 edited versions we read keep these.
5
Distinctive
This author's own choices. Worth a look.
4
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Distinctive: line 20
Write files, comments and reports in English, ASCII only.
- Distinctive: line 21
Use simple English: short sentences, common words, simple grammar.
- Very specific: line 30
Run uv --version. If it fails, stop and ask the user to install uv: https://docs.astral.sh/uv/getting-started/installation/
- Distinctive: line 35
Run git status --short. If it prints anything, stop and ask the user to commit or stash first.
- Very specific: line 40
If $version is empty, ask: "Which version?
- Very specific: line 42
Read ## Development in CHANGES.md.
- Distinctive: line 56
Check every place against the new version:
- Distinctive: line 62
Read git diff. Only the version and the new heading may change.
- Very specific: line 65
Commit, if the user asked for a commit: release: $version.
“Common” is measured: kept by at least 6 in 10 of the 40 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
Bump the version
Arguments
$version- the new version, such as1.2.3or1.2.3-rc.1, with nov. When it is missing, ask for it in step 1.
Communication
- Reply in the language the user writes in.
- Write files, comments and reports in English, ASCII only.
- Use simple English: short sentences, common words, simple grammar.
Models
- The current model does all of it. The script writes the files, so a small model is enough.
Before you start
- Run
uv --version. If it fails, stop and ask the user to install uv: https://docs.astral.sh/uv/getting-started/installation/ - A sandbox can stop uv from writing its cache. If a later
uv runreports that, set the variableUV_CACHE_DIRto.cache/uv, which git ignores, and run it again. Do not call Python directly, and do not edit the files by hand instead. - Run
git status --short. If it prints anything, stop and ask the user to commit or stash first. The bump must be an isolated diff.
Steps
- If
$versionis empty, ask: "Which version? Example: 1.2.3" - Read
## DevelopmentinCHANGES.md. If it is empty, stop: a version with no entries has no release notes. Use the check-changes skill first. Set the version. It moves the entries under the version, and prints the changed files as JSON.
uv run scripts/version/version.py bump $versionExit 2 means the version is wrong. Exit 1 means that a place states no version or that
CHANGES.mdbreaks a limit, and no file changed. In both cases, report the message and stop.Check every place against the new version:
uv run scripts/version/version.py check --tag v$version- Read
git diff. Only the version and the new heading may change. If anything else changed, stop and report it. - Commit, if the user asked for a commit:
release: $version. Do not tag and do not push. A person cuts the tag onmain, afterdevelopmerges there, because the tag starts the release workflow and publishes the binaries.
Done when
version.py check --tag v$versionexits with 0.
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.

