version-bumper
Skill1 starsChanged 6 days agoMITView on GitHub
Bump the project version everywhere it lives in one consistent pass — package.json, lockfile, nested/CLI package manifests, version constants, README badges, docs — then roll the changelog's Unreleased section under the new version and stage an annotated git tag. Use when you've already decided the new version (X.Y.Z or a pre-release like -rc.1) and need every artifact updated to the same value without drift, or before cutting a release.
- Installs packages
- Commits and pushes
4 other projects use a version of this.
Adopted by
Most recently taken up by
- davidgfolch/AI-job-searchtheir own version, first seen Nov 8, 2026
- Fu-Jie/awesome-openwebuitheir own version, first seen Oct 8, 2026
- Fu-Jie/openwebui-extensionstheir own version, first seen Oct 8, 2026
- bestdeejay-design/agent-skillstheir own version, first seen Aug 9, 2026
Other versions4 projects use a version of this.
Word for word · 0
None found.
Edited · 0
None found.
Wrote their own version · 4
- Fu-Jie/awesome-openwebui★ 326same name
- Fu-Jie/openwebui-extensions★ 326same name
- bestdeejay-design/agent-skills★ 6same name
- davidgfolch/AI-job-search★ 6same 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 repository163 other files it gives its agents.
- agents.mdAGENTS.md
- 3d-asset-handoff-sheetSkill
- accessibility-regression-auditorSkill
- adr-writerSkill
- agent-memory-designerSkill
- agent-trajectory-evaluatorSkill
- alerting-rules-tunerSkill
- analysis-memo-writerSkill
- annotation-disagreement-ledgerSkill
- annotation-task-spec-builderSkill
- api-deprecation-plannerSkill
- api-error-contract-designerSkill
- architecture-diagram-generatorSkill
- asset-metadata-review-ledgerSkill
- auth-flow-reviewerSkill
- background-job-reliability-auditorSkill
- branch-rebaserSkill
- brand-voice-profilerSkill
- bundle-analyzerSkill
- cache-policy-designerSkill
- canary-release-plannerSkill
- caption-correction-ledgerSkill
- changelog-from-prsSkill
- chart-chooserSkill
- chunking-strategy-optimizerSkill
- circular-dependency-breakerSkill
- claude-settings-auditorSkill
- code-example-verifierSkill
- cold-email-deliverability-auditorSkill
- cold-start-optimizerSkill
- commit-splitterSkill
- competitor-teardownSkill
- component-spec-writerSkill
- connection-pool-tunerSkill
- content-repurposerSkill
- contract-obligation-registerSkill
- contract-test-designerSkill
- conventional-commitsSkill
- cors-configuratorSkill
- coverage-gap-finderSkill
- crm-export-auditorSkill
- dashboard-designerSkill
- data-retention-auditorSkill
- dataset-first-lookSkill
- dead-code-finderSkill
- deadlock-diagnoserSkill
- decision-log-reconcilerSkill
- dependency-auditSkill
- dependency-upgrade-plannerSkill
- design-brief-writerSkill
- design-critique-checklistSkill
- design-token-extractorSkill
- devcontainer-designerSkill
- distributed-tracing-instrumenterSkill
- dockerfile-optimizerSkill
- email-sequence-drafterSkill
- embedding-index-tunerSkill
- embedding-set-inspectorSkill
- entity-match-candidate-ledgerSkill
- exit-ticket-builderSkill
- The first 60 shown.
The file
We split this skill into the rules it gives an agent
1 rule. 0 are common, 1 is distinctive, and 0 are very specific to this project.
0
Common
Most of the 4 edited versions we read keep these.
1
Distinctive
This author's own choices. Worth a look.
0
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Distinctive: line 24
Find every place the version lives: Don't assume — grep. The number leaks into more files than you expect:
“Common” is measured: kept by at least 6 in 10 of the 4 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
Bumping a version is rarely one line. The number hides in package.json, a lockfile, a nested CLI or submodule manifest, a __version__ constant, a README badge, and a docs install snippet — and any one you miss ships as drift. This skill finds every occurrence, sets them all to a single agreed value, rolls the changelog, and stages the tag. It never picks the version for you and never publishes without your say-so.
When to use this skill
- You've decided the new version (e.g.
2.4.0, or a pre-release2.4.0-rc.1) and need every artifact updated to match in one pass. - You're cutting a release and want the bump commit to be clean, atomic, and correctly tagged.
- A previous bump left drift —
package.jsonsays one version, the lockfile or a badge says another — and you want them reconciled. - You maintain a monorepo or a repo with a bundled CLI sub-package whose versions and dependency ranges must move together.
[!NOTE] This skill applies a version you've already chosen. If you haven't decided whether the change is major/minor/patch, run a semver analysis first (see
semver-advisor) — getting the number right is out of scope here.
Instructions
- Confirm the exact target version before touching anything. Read the current version from the root
package.json(orpyproject.toml,Cargo.toml, etc.). State the old → new transition explicitly and stop if the new value isn't strictly greater, or if it's malformed. A pre-release identifier (-rc.1,-beta.2,-next.0) is valid and must be carried verbatim into every artifact — do not silently drop it. Find every place the version lives. Don't assume — grep. The number leaks into more files than you expect:
OLD="1.2.3" # current version, escaped if it contains dots grep -rnF "$OLD" \ --include='*.json' --include='*.toml' --include='*.md' \ --include='*.ts' --include='*.js' --include='*.py' --include='*.yml' --include='*.yaml' \ --exclude-dir=node_modules --exclude-dir=.git --exclude-dir=dist .Then triage each hit. Update version declarations; never blanket-replace — a
1.2.3in changelog history or a test fixture must stay put.- Update the canonical manifest(s). Edit the
versionfield in the rootpackage.json. For nested packages (acli/package.json, workspace packages, a submodule manifest), update each one to the same value unless they version independently — confirm which model the repo uses before assuming lockstep. Update the lockfile so it doesn't drift. Editing
package.jsonalone leavespackage-lock.json(and thepackages[""].versionentry inside it) stale. Regenerate it deterministically rather than hand-editing:npm install --package-lock-only --ignore-scriptsFor
pnpmusepnpm install --lockfile-only; foryarnrunyarn install --mode update-lockfile.- Update version constants and human-facing references. Catch the non-manifest spots the grep surfaced: a
VERSION/__version__constant in source, a README shields.io badge (version-1.2.3-→version-2.4.0-), install snippets pinningpkg@1.2.3, and anydocs/page that names the current version. Skip historical mentions (changelog entries, migration notes about old releases). - Roll the changelog. Move everything under the
## [Unreleased]heading into a new## [X.Y.Z] — YYYY-MM-DDsection dated today, then leave## [Unreleased]empty above it. Update the link-reference footer if the changelog uses compare-URL refs ([X.Y.Z]: …/compare/vOLD...vX.Y.Zand a fresh[Unreleased]: …/compare/vX.Y.Z...HEAD). - For monorepos, keep interdependent versions and ranges consistent. When package A depends on package B and both bump, update A's dependency range on B (e.g.
"@scope/b": "^2.4.0") so a consumer doesn't resolve a mismatched pair. Verify noworkspace:*range was accidentally pinned to a literal. Stage — do not run — the release commit and annotated tag. Print the exact commands and wait for the user. The bump commit must land before the tag points at it; tag from the wrong commit and you've published a tag that doesn't match its tree.
git add -A git commit -m "chore(release): vX.Y.Z" git tag -a vX.Y.Z -m "vX.Y.Z" # push only when asked: git push origin HEAD vX.Y.Z
[!WARNING] Never run
git tagbefore the bump commit is committed — an annotated tag captures the commit it points to, so a premature tag will reference the previous state, and moving a published tag breaks anyone who already fetched it. Commit first, verifygit show HEAD --statcontains the version edits, then tag.
[!WARNING] A lockfile left at the old version is the single most common bump bug: CI installs, sees
package-lock.jsondisagrees withpackage.json, and either fails or silently resolves the old version. Always regenerate the lockfile in the same commit as the manifest bump.
Output
Two artifacts, both reviewable before anything is committed:
A change table of every file touched, old → new:
File Old New package.json1.2.32.4.0package-lock.json1.2.32.4.0cli/package.json1.2.32.4.0src/version.ts1.2.32.4.0README.md(badge)1.2.32.4.0CHANGELOG.mdUnreleased ## [2.4.0] — 2026-06-17The exact release commands, ready to paste and run only on request:
git add -A git commit -m "chore(release): v2.4.0" git tag -a v2.4.0 -m "v2.4.0" # git push origin HEAD v2.4.0Plus a one-line note of anything skipped on purpose (historical version mentions left untouched) or anything that needs a human decision (a sub-package that may version independently).
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.

