Agent skill

Version Bump

by skanehira in skanehira/ghost

Cargo.tomlのバージョンをセマンティックバージョニングに従ってバンプアップし、git tagを作成する。前回のgit tagからの差分を分析してバージョン種別(major/minor/patch)を自動判定する。「バージョンを上げて」「リリースして」「version bump」「バージョンアップ」などのリクエストで起動。

MITAuto-check passedDevelopment

Install Version Bump

skills CLI
$ npx skills add skanehira/ghost --skill version-bump -a claude-code

Project install by default; add -g for ~/.claude/skills/.

GitHub CLI
$ gh skill install skanehira/ghost version-bump --agent claude-code

Project scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).

Manual copy
$ git clone --depth 1 https://github.com/skanehira/ghost.git skills-src && mkdir -p .claude/skills && cp -r skills-src/.claude/skills/version-bump .claude/skills/version-bump && rm -rf skills-src

Use ~/.claude/skills/ instead of .claude/skills for a personal install. The folder must contain SKILL.md.

Claude Code skills documentation · loads skills from .claude/skills/

Facts

Skill name
version-bump
GitHub stars
155
Token cost
~390 tokens
SKILL.md length
57 words
Files
1
Skills in repo
1
Repo updated
First seen
Licence
MIT

At a glance

Cargo.tomlのバージョンをセマンティックバージョニングに従ってバンプアップし、git tagを作成する。前回のgit tagからの差分を分析してバージョン種別(major/minor/patch)を自動判定する。「バージョンを上げて」「リリースして」「version bump」「バージョンアップ」などのリクエストで起動。

  • Works in 5 steps: 現在の状態を分析 → バージョン種別を判定 → ユーザーに提案 → …
  • Tasks that involve Git workflow
  • SKILL.md covers ワークフロー and 注意事項
  • Calls git and cargo

What it does

Version Bump is an agent skill from skanehira/ghost. Cargo.tomlのバージョンをセマンティックバージョニングに従ってバンプアップし、git tagを作成する。前回のgit tagからの差分を分析してバージョン種別(major/minor/patch)を自動判定する。「バージョンを上げて」「リリースして」「version bump」「バージョンアップ」などのリクエストで起動。

Its SKILL.md is about 390 tokens, which your agent loads only when the skill is triggered. It is a single SKILL.md file with no bundled scripts.

It sits in Development, covering Git workflow. It works with Git and Rust. The repository describes itself as: Simple background process manager for Unix systems. The licence is MIT.

When your agent uses it

  • Tasks that involve Git workflow

Example prompts

  • “/version-bump”

Workflow steps

5 steps, taken from the step headings in SKILL.md.

  1. 現在の状態を分析
  2. バージョン種別を判定
  3. ユーザーに提案
  4. バージョンを更新
  5. 完了報告

What it can do on your machine

Read from SKILL.md and the folder at commit 27f744c. It shows what the files ask for, not the result of running them.

  • Tool permissions

    Pre-approves nothing: there is no allowed-tools line, so your agent's usual permission prompts apply.

    From allowed-tools in the SKILL.md frontmatter.

  • Runs code

    Shell commands in SKILL.md call:

    • git
    • cargo

    From the folder's file list and the shell code blocks in SKILL.md.

  • Network

    No URLs in SKILL.md. Its commands use git, which can reach the network depending on how they are called.

    From URLs in SKILL.md, links to its own repository left out.

  • Credentials

    Names no API keys, tokens, secrets or passwords.

    From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.

Context cost

Version Bump loads about 390 tokens when it runs. Until then it costs about 45 tokens; SKILL.md has 57 words of instructions outside code blocks.

Always · name and description, kept in context so the agent knows when to use it
~45
When it runs · the whole SKILL.md, loaded when a task matches
~390

Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.

Safety

Auto-check passed

The automated check found no risky patterns in SKILL.md.

Automated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); files beside SKILL.md are not scanned.

SKILL.md

The full file from skanehira/ghost at commit 27f744c, republished under its MIT licence (© skanehira). 57 words, ~390 tokens.

Download SKILL.mdSave it as .claude/skills/version-bump/SKILL.md (or your agent's skills folder).
name
version-bump
description
Cargo.tomlのバージョンをセマンティックバージョニングに従ってバンプアップし、git tagを作成する。前回のgit tagからの差分を分析してバージョン種別(major/minor/patch)を自動判定する。「バージョンを上げて」「リリースして」「version bump」「バージョンアップ」などのリクエストで起動。

Version Bump

Cargo.tomlのバージョンをバンプアップし、git tagを作成する。

ワークフロー

1. 現在の状態を分析
bash
# 最新のバージョンタグを取得
git describe --tags --abbrev=0 2>/dev/null || echo "v0.0.0"

# 前回タグからの差分を取得
git diff <前回タグ>..HEAD --stat
git diff <前回タグ>..HEAD
2. バージョン種別を判定

差分の内容を分析し、以下の基準でバージョン種別を判定:

種別判定基準
major破壊的変更:パブリックAPIのシグネチャ変更、削除、互換性のない変更
minor機能追加:新しいパブリック関数/構造体/モジュールの追加、新機能
patchバグ修正:既存機能の修正、リファクタリング、ドキュメント更新、依存関係更新
3. ユーザーに提案

判定結果をユーザーに提示し、AskUserQuestionで確認:

現在のバージョン: X.Y.Z
提案バージョン: X.Y.Z+1 (patch)

主な変更点:
- [変更内容のサマリー]

このバージョンでよろしいですか?

選択肢:

  • 提案通り (patch/minor/major)
  • 別のバージョン種別を選択
4. バージョンを更新

ユーザー承認後:

  1. Cargo.tomlのversionフィールドを更新
  2. cargo checkで検証
  3. cargo testで全テスト通過を確認(必須: バージョン文字列がテストの期待値に含まれている場合の不整合をここで検出する)
  4. 変更をコミット: chore: bump version to X.Y.Z
  5. git tagを作成: vX.Y.Z

テストが失敗した場合は、コミットせずにユーザーに報告して原因を特定する。バージョン文字列由来の失敗であれば、テスト側を動的化(例: env!("CARGO_PKG_VERSION"))するか期待値ファイルを更新する。

5. 完了報告
バージョンを v{新バージョン} に更新しました。

git push && git push --tags でリモートに反映してください。

注意事項

  • タグはvプレフィックス付き(例: v1.2.3)
  • Cargo.lockが存在する場合は自動更新される
  • ワークスペースの場合はルートのCargo.tomlのみ更新

© skanehira, MIT. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file

Files

Just SKILL.md in .claude/skills/version-bump of skanehira/ghost.

Open the folder on GitHubat commit 27f744c

Compare with similar skills

Version Bump next to the 5 skills that share the most tags, products or categories with it. Stars are the repository's; “used in” counts other GitHub owners with a copy.

Version Bump compared with similar skills
SkillStarsUsed inTokensAuto-checkLicenceRepo updated
Version Bump this skillskanehira/ghost155—~390Automated safety check: PassMIT
Worktrunk Release Workflowmax-sixty/worktrunk9k—~6.9kAutomated safety check: PassCustom licence
BrDicklesworthstone/beads_rust1.1k—~2.7kAutomated safety check: PassMIT
Guarded Git Commit and Pushjerrywu001/cc-sessions-viewer394—~603Automated safety check: NotesMIT
Stax Devcesarferreira/stax129—~987Automated safety check: PassMIT
Radicle Ecosystemradicle-dev/radicle-explorer148—~574Automated safety check: PassGPL-3.0

Similar skills

  • Worktrunk Release Workflow

    max-sixty/worktrunk

    Walks a maintainer through cutting a Worktrunk release: sync the release branch, pass two test gates, review the changes, then publish.

    9k GitHub stars~6.9k tokensUpdated today
    DevelopmentAuto-check passed
  • Br

    Dicklesworthstone/beads_rust

    Official skill for beadsrust (br), a local-first, dependency-aware issue tracker for AI agents.

    1.1k GitHub stars~2.7k tokensUpdated today
    DevelopmentAuto-check passed
  • Guarded Git Commit and Push

    jerrywu001/cc-sessions-viewer

    Commits and pushes only on an explicit request, pulling first, running the project's CI checks locally, and stopping cold on any conflict or failure.

    394 GitHub stars~603 tokensUpdated yesterday
    DevelopmentAuto-check: notes
  • Stax Dev

    cesarferreira/stax

    Development harness for the stax Rust CLI project. An agent skill from cesarferreira/stax.

    129 GitHub stars~987 tokensUpdated today
    DevelopmentAuto-check passed
  • Radicle Ecosystem

    radicle-dev/radicle-explorer

    Map of the sibling Radicle repositories that radicle-httpd depends on (heartwood, radicle-git, radicle-job, rips, radicle.dev), with the key crates and files to read in each.

    148 GitHub stars~574 tokensUpdated 2 days ago
    DevelopmentAuto-check passed
  • Add Tauri Command

    devlint/GitWand

    A skill your agent uses when the user wants to expose a Rust feature to the Vue frontend, add a Tauri IPC command, invoke something from a Vue component, or wire up any backend/frontend…

    180 GitHub stars~1.5k tokensUpdated today
    DevelopmentAuto-check passed

Works with

Categories

Questions about Version Bump

What does Version Bump do?

Cargo.tomlのバージョンをセマンティックバージョニングに従ってバンプアップし、git tagを作成する。前回のgit tagからの差分を分析してバージョン種別(major/minor/patch)を自動判定する。「バージョンを上げて」「リリースして」「version bump」「バージョンアップ」などのリクエストで起動。. Version Bump is an agent skill from skanehira/ghost.

When should I use Version Bump?

Version Bump fits situations like: tasks that involve Git workflow.

How do I install Version Bump in Claude Code?

Run `npx skills add skanehira/ghost --skill version-bump -a claude-code`. Or copy the skill folder (.claude/skills/version-bump in skanehira/ghost) into .claude/skills/version-bump in your project. Claude Code loads it when a task matches its description.

How do I install Version Bump in Codex?

Run `npx skills add skanehira/ghost --skill version-bump -a codex`. Or copy the skill folder (.claude/skills/version-bump in skanehira/ghost) into .agents/skills/version-bump in your project. Codex loads it when a task matches its description.

Can I use Version Bump in Cursor, Gemini CLI or GitHub Copilot?

Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add skanehira/ghost --skill version-bump -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/version-bump, .gemini/skills/version-bump, .github/skills/version-bump and .opencode/skills/version-bump in your project.

What does Version Bump need to run?

Going by SKILL.md and its folder, Version Bump needs the command-line tools its instructions call (git and cargo).

Does Version Bump access the network?

SKILL.md contains no URLs. Its commands use git, which can reach the network depending on how they are called. This is read from the text; nothing was executed.

Is Version Bump safe to install?

Our automated static check of SKILL.md found no risky patterns, such as piping downloads into a shell, reading credential files or hidden Unicode. It is not a guarantee. Review the folder before installing.

What licence does Version Bump use?

Version Bump is published under the MIT licence (the repository's licence). It allows redistribution, so the full SKILL.md is shown on this page.

How many tokens does Version Bump use?

About 390 tokens (SKILL.md is roughly 1.6k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full.

What are the alternatives to Version Bump?

Skills that share tags, products or a category with Version Bump: Worktrunk Release Workflow (max-sixty/worktrunk, 9k stars), Br (Dicklesworthstone/beads_rust, 1.1k stars), Guarded Git Commit and Push (jerrywu001/cc-sessions-viewer, 394 stars) and Stax Dev (cesarferreira/stax, 129 stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.

Who maintains Version Bump?

skanehira (a GitHub user) maintains it in skanehira/ghost, which has 155 GitHub stars. The repository was last updated on May 25, 2026.

Source: skanehira/ghost on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.