bump-version
Skill14 starsChanged 32 days agoApache-2.0View on GitHub
Bump the KamehaDB app version across all 3 package files (root, desktop, and shared package.json) and update CHANGELOG.md. Use when the user wants to release a new version, bump the version, cut a release tag, or update the changelog.
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
- 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★ 882same 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 repository17 other files it gives its agents.
- AGENTS.mdAGENTS.md
- landing/AGENTS.mdAGENTS.md
- CLAUDE.mdCLAUDE.md
- brainstorm-featureSkill
- context-handoffSkill
- document-wikiSkill
- estimate-featureSkill
- implement-taskSkill
- lean-auditSkill
- plan-featureSkill
- preparing-releasesSkill
- read-codebase-contextSkill
- review-and-verifySkill
- setup-codebaseSkill
- setup-openezSkill
- systematic-debuggingSkill
- using-devkitSkill
The file
We split this skill into the rules it gives an agent
8 rules. 0 are common, 6 are distinctive, and 2 are very specific to this project.
0
Common
Most of the 40 edited versions we read keep these.
6
Distinctive
This author's own choices. Worth a look.
2
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Distinctive: line 27
Run these commands to inspect recent commits since the last version:
- Distinctive: line 37
Use Semantic Versioning rules:
- Distinctive: line 43
If the user specifies a version, use that.
- Distinctive: line 49
Ask the user to confirm the target version before proceeding.
- Very specific: line 63
Read CHANGELOG.md and find the ## [Unreleased] section (just below the header).
- Very specific: line 102
Write concise, user-facing descriptions (not raw commit messages).
- Distinctive: line 104
If there are no commits in a category, omit that section entirely.
- Distinctive: line 108
Run a quick check that all files have the same 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 Version
This workflow updates the KamehaDB app version across all files that contain it, and updates the CHANGELOG.
Version locations
The version string must be updated in all of these files (they must stay in sync):
| # | File | Field |
| 1 | package.json | "version" |
| 2 | apps/desktop/package.json | "version" |
| 3 | packages/shared/package.json | "version" |
Note:
landing/package.jsonhas its own independent version (0.1.0) — do NOT touch it. Note: the version shown inside the app comes fromgit describe --tags(seeapps/desktop/vite.config.ts) — tagging the release is what updates the in-app version string.
Steps
1. Determine the new version
Run these commands to inspect recent commits since the last version:
# Show the current version
grep '"version"' package.json | head -1
# Show commits since the last version tag
git log --oneline $(git describe --tags --abbrev=0 2>/dev/null || echo HEAD~50)..HEAD --oneline 2>/dev/null || git log --oneline -30Use Semantic Versioning rules:
- Patch (e.g.
1.4.0→1.4.1): bug fixes only, no new features. - Minor (e.g.
1.4.0→1.5.0): new features added, backward compatible. - Major (e.g.
1.4.0→2.0.0): breaking changes.
If the user specifies a version, use that. Otherwise, analyze the commit messages:
- Commits with
feat:orfeat(scope):→ at least a minor bump. - Commits with
fix:orfix(scope):only → patch bump. - Commits with
BREAKING CHANGEor!:→ major bump.
Ask the user to confirm the target version before proceeding.
2. Update version in all 3 files
Edit each file listed in the table above. Replace the old version string with the new one.
Example for package.json:
"version": "1.5.0"3. Update CHANGELOG.md
Read CHANGELOG.md and find the ## [Unreleased] section (just below the header).
Replace ## [Unreleased] with the new version and today's date, then add a fresh ## [Unreleased] section above it.
The format should be:
## [Unreleased]
---
## [v1.5.0] — 2026-07-10
### Added
- **Feature name** — brief description.
### Changed
- **Change name** — brief description.
### Fixed
- **Fix name** — brief description.To fill in the changelog content, analyze the git log since the previous version tag:
git log --oneline $(git describe --tags --abbrev=0 2>/dev/null)..HEADCategorize commits into:
- Added —
feat:commits - Changed —
refactor:,perf:, or behavior-changing commits - Fixed —
fix:commits - Removed —
revert:or removal commits (if any)
Write concise, user-facing descriptions (not raw commit messages). Use the **Feature name** — description. pattern from existing entries.
If there are no commits in a category, omit that section entirely.
4. Verify
Run a quick check that all files have the same version:
# // turbo
grep -r '"1.5.0"' package.json apps/desktop/package.json packages/shared/package.json(Replace 1.5.0 with the actual new version.)
5. Summary
Present to the user:
- The old version → new version
- List of files updated
- A preview of the CHANGELOG entry
- Suggest committing with:
git add -A && git commit -m "chore: bump version to vX.Y.Z"
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.

