version-bump

Bump semantic versions across project files and create git tags and GitHub releases.

Updated Aug 23, 2026
One-click install
npx skills add https://github.com/gahoccode/PRDs --skill version-bump-gahoccode
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: version-bump
Source: https://github.com/gahoccode/PRDs/tree/main/skills/version-bump
Command: npx skills add https://github.com/gahoccode/PRDs --skill version-bump-gahoccode

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill streamlines semantic versioning across project ecosystems by updating all version-tracked files (e.g., package.json, pyproject.toml), creating git tags, GitHub releases, and generating a CHANGELOG from releases.

Core Features & Use Cases

  • Multi-file versioning: updates major version references across multiple files.
  • Git & releases: creates annotated tags and GitHub releases.
  • CHANGELOG generation: auto-generates changelog entries from releases.

Quick Start

  1. Determine the target version (PATCH, MINOR, MAJOR).
  2. Update all version files to the new version (e.g., 5.3.1).
  3. Commit, tag, push, and create a GitHub release with notes.

Frequently Asked Questions about version-bump

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

FAQPage Schema
How do I automate semantic version bumps across multiple project files?

Semantic version bumping automates incrementing version numbers using PATCH, MINOR, or MAJOR increments across all tracked files like package.json and pyproject.toml. This Skill applies the chosen increment, updates every version reference, creates git tags, and generates a GitHub release in one operation.

Can I bump versions in both Node.js and Python projects at the same time?

Yes. This Skill handles multi-ecosystem versioning by updating package.json, pyproject.toml, and other metadata files (marketplace.json, plugin.json) in a single operation, ensuring version consistency across Node.js and Python codebases.

How do I generate a CHANGELOG automatically from version releases?

After bumping versions, this Skill auto-generates CHANGELOG.md entries from your releases, eliminating manual changelog maintenance. It creates annotated git tags and pushes GitHub releases with integrated release notes.

What's the best way to keep versions synchronized across a monorepo or multi-file project?

Version synchronization across projects requires updating all version-tracked files consistently in a single transaction. This Skill verifies consistency across files after incrementing, preventing version drift between package.json, pyproject.toml, and other metadata.

Does this work with GitHub releases and git tagging?

Yes. The Skill creates annotated git tags in vX.Y.Z format, pushes changes to your repository, and publishes GitHub releases automatically as part of the versioning workflow.

What happens if version files are missing or malformed?

This Skill verifies consistency across all version files before and after updates. If files are missing or contain invalid version strings, the operation detects inconsistencies; ensure all target files exist and follow semantic versioning format before running.