agentleFS
asta-nguyenasta-nguyen/kamehadb/.agents/skills/bump-version/SKILL.md

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

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-LtdSkill

    oss-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-LtdSkill

    pr-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

  • volovelySkill

    pr-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

  • lbednerSkill

    i18n

    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

  • AnthropicSkill

    architecture

    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

  • NVIDIASkill

    testing

    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

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
  1. Distinctive:

    Run these commands to inspect recent commits since the last version:

    line 27
  2. Distinctive:

    Use Semantic Versioning rules:

    line 37
  3. Distinctive:

    If the user specifies a version, use that.

    line 43
  4. Distinctive:

    Ask the user to confirm the target version before proceeding.

    line 49
  5. Very specific:

    Read CHANGELOG.md and find the ## [Unreleased] section (just below the header).

    line 63
  6. Very specific:

    Write concise, user-facing descriptions (not raw commit messages).

    line 102
  7. Distinctive:

    If there are no commits in a category, omit that section entirely.

    line 104
  8. Distinctive:

    Run a quick check that all files have the same version:

    line 108

“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.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
SKILL.md

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):

#FileField
1package.json"version"
2apps/desktop/package.json"version"
3packages/shared/package.json"version"

Note: landing/package.json has its own independent version (0.1.0) — do NOT touch it. Note: the version shown inside the app comes from git describe --tags (see apps/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 -30

Use 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: or feat(scope): → at least a minor bump.
  • Commits with fix: or fix(scope): only → patch bump.
  • Commits with BREAKING CHANGE or !: → 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)..HEAD

Categorize 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"

Download now (ZIP)

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
What did you use it for? e.g. Reviewing pull requests in a Rails app

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.