kamehadb: Skill for Claude Code

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