skills.rest
dhnt
dhntOFFICIAL
Explore all skills by this author →
GitHub

bump-version

Analyze changes since the last release tag to select a semantic version increment.

Updated Dec 21, 2018
Search Tags:#release management#git tags#semver#version bump#changelog hygiene#CI testing
One-click install
npx skills add https://github.com/dhnt/dhnt --skill bump-version-dhnt
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: bump-version
Source: https://github.com/dhnt/dhnt/tree/main/catalog/md/release/bump-version
Command: npx skills add https://github.com/dhnt/dhnt --skill bump-version-dhnt

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill prevents inconsistent or risky release versioning by guiding you to choose the correct semver bump based on the changes made since the last tag.

Core Features & Use Cases

  • Determines semver impact: Classifies changes into Breaking (MAJOR), New features (MINOR), and Bug fixes/docs/internal (PATCH).
  • Keeps version references in sync: Locates all places the version is stored and updates them together to avoid mismatches.
  • Supports pre-release cycles: Applies alpha/beta/rc pre-release tag conventions when needed.
  • Use case: Preparing a release for a repo where the version appears in multiple files (manifests, lockfiles, or a VERSION file) and must be updated consistently before tagging.

Quick Start

Tell the AI to bump the project version for the current release by inspecting the diff since the last git tag and updating every location where the version string appears.

Frequently Asked Questions about bump-version

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

FAQPage Schema
How do I pick the right semver bump for my release?▼

To pick the right semver bump, analyze changes since the last git tag and classify them into Breaking for MAJOR, new features for MINOR, and bug fixes or internal changes for PATCH increments.

How do I update version strings across multiple repository files?▼

Update version strings by locating every place the version is stored across manifests, lockfiles, or VERSION files, then applying the new semantic version simultaneously to avoid reference mismatches.

When do I need to use pre-release tags for semantic versioning?▼

Use semver pre-release tags during ongoing release cycles when you need to apply alpha, beta, or rc conventions to your version string before finalizing a stable release boundary.

Does semantic versioning work with continuous integration testing?▼

Semantic versioning integrates with CI testing by running build and test suites after updating all version locations, ensuring the newly bumped release tag passes checks before committing.

What is the best way to maintain changelog hygiene during a version bump?▼

Maintain changelog hygiene by establishing a consistent boundary between release commits and feature work, categorizing changes accurately, and preparing a clean commit message for the tag.

Related Skills

Explore More Product & Management Skills→
PlagueHOPlagueHO
4

release-changelog

Update CHANGELOG.md and create a release tag from commits since the last version tag.

Community
Advanced
guardiatechnologyguardiatechnology

kata-tag

Create annotated GPG-signed Git release tags with SemVer 2.0 rules.

Official
Advanced
NITRR-OfficialNITRR-Official
4

release-management

Automate semantic versioning, changelog generation, and GitHub release creation for CampusOS.

Official
Intermediate
ether-moonether-moon

bumping-version

Automates semantic versioning and changelog updates for the knowledge-distillery plugin.

Community
Intermediate