bump-version

Bump project versions, update CHANGELOG entries, and commit changes atomically.

Updated Mar 11, 2026
One-click install
npx skills add https://github.com/prata0x/gfo --skill bump-version-prata0x
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: bump-version
Source: https://github.com/prata0x/gfo/tree/main/.claude/skills/bump-version
Command: npx skills add https://github.com/prata0x/gfo --skill bump-version-prata0x

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

バージョン番号の更新と CHANGELOG の記入・関連コミット作業を手作業で行う煩雑さを解消します。複数のファイル編集を伴うリリース準備を一括で行い、ヒューマンエラーを減らします。

Core Features & Use Cases

  • バージョン番号の自動更新とタグ付け
  • CHANGELOG の自動追記と整形
  • 変更を1つのコミットにまとめて履歴を整理 このスキルは「バージョンアップ」「bump」と言われたときに使えます。

Quick Start

最新のブランチで新バージョンを決定し、CHANGELOG を追記して変更をコミットしてください。

Frequently Asked Questions about bump-version

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I automate version bumps and changelog updates in a single commit?

To automate version bumps and changelog updates in a single commit, this Skill modifies the project version, appends changelog entries, and bundles all changes into one atomic commit. It handles explicit version ranges and HEAD-to-range scenarios to streamline release workflows.

What is the best way to update __version__ in code and modify the changelog together?

The best way to update __version__ in code and modify the changelog together is using an automated bump process. This Skill updates the version string, formats changelog entries, and commits the changes atomically to prevent manual editing errors.

Does this version bumping process work with standard Git release workflows?

Yes, this version bumping process works with standard Git release workflows. It determines the new version on the latest branch, updates the changelog, and creates a single commit to keep your repository history clean and organized.

Can I specify explicit version ranges when automating a release commit?

Yes, you can specify explicit version ranges when automating a release commit. The Skill handles both explicit version ranges and HEAD-to-range scenarios to accurately update the changelog and project version across your repository.

Why should I automate project version bumps instead of editing files manually?

You should automate project version bumps to eliminate the complexity and human error of manually editing multiple files. Automating this process updates the version and changelog atomically, ensuring consistent release preparation across your repository.