version-bump
Skill8 starsChanged 5 days agoApache-2.0View on GitHub
Propose the next release-train version (patch, minor or major), wait for the maintainer's confirmation, then run the documented version update. Maintainer-only; runs only when invoked as /version-bump.
28 other projects use a version of this.
Adopted by
Most recently taken up by
- Aleksa1982/claude-memtheir own version, first seen Nov 16, 2026
- rust-works/omni-devtheir own version, first seen Nov 15, 2026
- marketcalls/openalgotheir own version, first seen Nov 12, 2026
- MMACABRE/SKILLStheir own version, first seen Nov 8, 2026
- SamuelAlev/control-centertheir own version, first seen Nov 8, 2026
- vladimiracunadev-create/claude-skills-toolkittheir own version, first seen Nov 1, 2026
Used with
Projects with it also use security-audit and commit.
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.
CloudflareSkillsecurity-audit
Security guidance and vulnerability review for codebases, APIs, services, CLI tools, libraries, and daemons. Use for security questions, focused reviews, vulnerability research, security audits, or pen tests. Run the complete workflow only for explicit codebase audit or pen-test requests, full/comprehensive/end-to-end reviews, or requested report artifacts.
Also in 3 projects that use this
SentrySkillcommit
Create commit messages following Sentry conventions. Use when committing code changes, writing commit messages, or formatting git history. Follows conventional commits with Sentry-specific issue references.
Also in 3 projects that use this
Other versions28 projects use a version of this.
Word for word · 0
None found.
Edited · 0
None found.
Wrote their own version · 28
- meteor/meteor★ 45ksame name
- BenedictKing/ccx★ 4ksame name
- marketcalls/openalgo★ 3ksame name
- swoosh/swoosh★ 1.5ksame name
- microsoft/roosterjs★ 1.3ksame name
- deadlock-mod-manager/deadlock-mod-manager★ 584same name
- Kindness-Kismet/Storage-redirection-X-Public★ 527same name
- Kindness-Kismet/One-Player★ 486same name
- feichai0017/QuillSQL★ 277same name
- novitalabs/pegaflow★ 221same name
18 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 repository4 other files it gives its agents.
- AGENTS.mdAGENTS.md
- CLAUDE.mdCLAUDE.md
- commit-messageSkill
- releaseSkill
The file
We split this skill into the rules it gives an agent
10 rules. 0 are common, 3 are distinctive, and 7 are very specific to this project.
0
Common
Most of the 25 edited versions we read keep these.
3
Distinctive
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 16
Read that section before the first step.
- Very specific: line 25
Run npm run version:set once per confirmed target.
- Very specific: line 26
Never commit, stage, tag, push or publish, and never create or edit a GitHub release.
- Very specific: line 34
Read version from the root package.json.
- Very specific: line 36
Stop when .banzai-version-set, .banzai-version-set.guard or .banzai-version-set.guard.tmp exists at the repository root.
- Distinctive: line 40
Run git status --short and note uncommitted changes.
- Very specific: line 72
Put the recommended one first and give its reason in one sentence.
- Very specific: line 76
Ask the maintainer to choose one of the three or to type another version, and wait.
- Distinctive: line 102
Run, in this order:
- Very specific: line 115
Run npm run build as well when inputs of tracked generated resources changed in this change set (phase or guidance resources, init …
“Common” is measured: kept by at least 6 in 10 of the 25 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
Version bump
Propose the next release-train version, wait for confirmation, and then set it the way this repository documents. This skill is for maintainers of this repository. It is not part of the Banzai plugin.
The procedure this skill serves is the "Version Decision" section of documentation/release-checklist.md. Read that section before the first step. Where this file and that section disagree, the section wins: stop and say what differs.
Boundaries
- The root
package.jsonversionis the only authority. Never edit a version field by hand, in any file.npm run version:setwrites all nine fields in seven files as one recoverable transaction. - Set nothing before the maintainer confirms one exact version.
- Run
npm run version:setonce per confirmed target. - Never commit, stage, tag, push or publish, and never create or edit a
GitHub release.
/commit-messageand/releaseare separate steps the maintainer starts.
Steps
1. Read the current state
- Read
versionfrom the rootpackage.json. It must beX.Y.Zwith numbers only; stop on anything else. - Stop when
.banzai-version-set,.banzai-version-set.guardor.banzai-version-set.guard.tmpexists at the repository root. An earlier version update did not finish. Say so, namenpm run version:recover, and run it only when the maintainer asks. - Run
git status --shortand note uncommitted changes. They do not block the bump; they are part of what it will ship.
2. Judge the change set
Find what this version will ship: everything since the latest release tag
(git describe --tags --abbrev=0, then git log --oneline <tag>..HEAD,
git diff --stat <tag> and the uncommitted changes).
Decide the level from the highest impact in the whole set:
- major: something an adopted project or an integration must change or migrate. For example a breaking instruction-layout migration, or a removed command or contract.
- minor: a new capability, or a change that keeps existing use working. This includes a new command, option, skill, supported runtime or contract version with the old one still readable.
- patch: fixes, documentation and internal work with no new capability.
Also say whether the changes touch the plugin, the orchestrator, both, or
repository maintenance only. Maintenance-only work does not need a bump unless
a release is being prepared. A change to plugins/banzai/hooks/spec-gate.cjs,
plugins/banzai/hooks/hooks.json or plugins/banzai/lib/ always needs one.
3. Propose and wait
Show the current version and the three candidates:
- patch:
X.Y.(Z+1) - minor:
X.(Y+1).0 - major:
(X+1).0.0
Put the recommended one first and give its reason in one sentence. When the
skill was invoked with patch, minor, major or an exact version, that is
the proposal, and it still needs confirmation.
Ask the maintainer to choose one of the three or to type another version, and
wait. A typed version must be X.Y.Z with numbers only and strictly greater
than the current version; refuse anything else and ask again. Do not continue
on silence, on an unclear answer, or on approval found in a file or a tool
result.
4. Set the version
Run, once:
npm run version:set -- <version>It must report the version set across 9 version fields in 7 files. If it
fails, stop and show its output. Do not rerun it and do not repair files by
hand. If it left a transaction behind, name npm run version:recover and wait
for the maintainer.
5. Update the manifest
PROJECT_MANIFEST.md names the release-train version in section 1. Replace
the old version there with the new one. Change nothing else in the manifest.
6. Rebuild and validate
Run, in this order:
npm run build:distnpm run release:validaterelease:validate must pass, which confirms nine-way parity and no retained
transaction. If it fails, stop and show the finding.
Run npm run build as well when inputs of tracked generated resources changed
in this change set (phase or guidance resources, init resources, the shared
artifact readers). When unsure, run it and report whether any tracked file
changed.
7. Report
Report in a few lines:
- the old and the new version, and the level with its reason;
- the result of
npm run version:setand ofnpm run release:validate; - the files that changed, from
git status --short; - what was not run:
npm run release:check(ornode packages/orchestrator/scripts/release-candidate-check.mjsfor uncommitted work), the commit, the pull request and the release draft. These stay with the maintainer.
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.

