Back to list
henkisdabro

version-bump

by henkisdabro

A fast, beautiful TUI for managing MCP (Model Context Protocol) servers in Claude Code. Optimize your context window by enabling only the servers you need, when you need them.

1🍴 0📅 Jan 9, 2026

SKILL.md


name: version-bump description: Bump semantic version across all project files (package.json, CLI, README, docs). Use for version updates without full release. allowed-tools:

  • Read
  • Edit
  • Glob
  • Grep
  • Bash(npm run build)
  • Bash(npm test)
  • Bash(npm install:*)
  • Bash(node:*)
  • Bash(echo:*)
  • AskUserQuestion user-invocable: false

Version Bump Skill

Updates semantic version consistently across all project files. This skill handles version updates only - use /release for the full release workflow including git and npm publishing.

Trigger Words

Use when user says: "bump version", "update version", "version bump", or when called by the release skill.

Version Locations (Canonical List)

These are ALL locations where version numbers appear. Every bump MUST update all of these:

Primary Sources

FileLinePatternExample
package.json3"version": "X.Y.Z""version": "2.1.0"
src/cli/index.ts18const VERSION = 'X.Y.Z';const VERSION = '2.1.0';

Documentation

FileLinePatternExample
README.md12> **vX.Y.Z**:> **v2.1.0**:
docs/index.html45"softwareVersion": "X.Y.Z""softwareVersion": "2.1.0"

Auto-generated (DO NOT edit manually)

FileNotes
package-lock.jsonUpdated by npm install --package-lock-only

Procedure

Step 1: Determine New Version

Ask user or determine from context:

TypePatternWhen to Use
patchX.Y.Z+1Bug fixes, minor changes
minorX.Y+1.0New features, backwards compatible
majorX+1.0.0Breaking changes

Or accept explicit version like "2.1.0".

Step 2: Read Current Version

node -p "require('./package.json').version"

Step 3: Update All Locations (IN ORDER)

  1. package.json (line 3):

    "version": "NEW_VERSION",
    
  2. src/cli/index.ts (line 18):

    const VERSION = 'NEW_VERSION';
    
  3. README.md (line 12):

    > **vNEW_VERSION**: [brief description of changes]
    
  4. docs/index.html (line 45):

    "softwareVersion": "NEW_VERSION",
    

Step 4: Update Lock File

npm install --package-lock-only

Step 5: Build

npm run build

Step 6: Verify

# All versions should match
echo "package.json: $(node -p "require('./package.json').version")"
echo "CLI binary:   $(node dist/cli.js --version)"

# Tests should pass
npm test

Verification Checklist

Before completing, verify ALL match the new version:

  • package.json version field
  • src/cli/index.ts VERSION constant
  • README.md version banner
  • docs/index.html softwareVersion
  • npm run build succeeds
  • npm test passes
  • node dist/cli.js --version outputs correct version

Semantic Versioning Reference

Change TypeVersion PartReset
Bug fixPatch (Z)None
New featureMinor (Y)Patch → 0
Breaking changeMajor (X)Minor → 0, Patch → 0

Examples:

  • 2.0.3 + patch = 2.0.4
  • 2.0.3 + minor = 2.1.0
  • 2.0.3 + major = 3.0.0

Notes

  • Never edit package-lock.json manually
  • The README version banner should include a brief changelog note
  • Always run build and tests after version bump
  • This skill does NOT commit changes - use /release for full workflow

Use /release for full release workflow including:

  • Version bump (this skill)
  • Git commit
  • Git tag
  • Push to remote
  • GitHub release creation
  • Automatic npm publish via OIDC

Score

Total Score

75/100

Based on repository quality metrics

SKILL.md

SKILL.mdファイルが含まれている

+20
LICENSE

ライセンスが設定されている

+10
説明文

100文字以上の説明がある

+10
人気

GitHub Stars 100以上

0/15
最近の活動

3ヶ月以内に更新

+5
フォーク

10回以上フォークされている

0/5
Issue管理

オープンIssueが50未満

+5
言語

プログラミング言語が設定されている

+5
タグ

1つ以上のタグが設定されている

+5

Reviews

💬

Reviews coming soon