skills.rest
rust-works
rust-worksOFFICIAL
Explore all skills by this author →
GitHub

version-bump

Determine semantic version bumps from commits and diffs.

10|2|Updated Aug 23, 2025
Search Tags:#semver#semantic-versioning#breaking-change#version-bump#release-planning#major-minor-patch
One-click install
npx skills add https://github.com/rust-works/omni-dev --skill version-bump-rust-works
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: version-bump
Source: https://github.com/rust-works/omni-dev/tree/main/.claude/skills/version-bump
Command: npx skills add https://github.com/rust-works/omni-dev --skill version-bump-rust-works

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill helps teams determine the correct semantic version bump (MAJOR, MINOR, PATCH) based on observed changes, ensuring releases reflect API impact and feature additions.

Core Features & Use Cases

  • Rule-based version bump decisions: Applies semantic versioning rules to changes and categorizes them as MAJOR, MINOR, or PATCH.
  • Release planning support: Guides teams through planning and documenting appropriate bumps for upcoming releases.
  • Diff and impact consideration: Considers breaking changes, new features, bug fixes, and compatibility constraints to justify the bump.
  • Use Case: When preparing a new release after a set of commits, use this skill to determine the correct bump and rationale for the version tag.

Quick Start

Use the version-bump skill to evaluate changes since the last release and output a recommended semantic version bump.

Frequently Asked Questions about version-bump

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

FAQPage Schema
How do I determine the correct semantic version bump for my new release?▼

To determine the correct semantic version bump, you evaluate observed changes like breaking changes, new features, and bug fixes. The version-bump skill categorizes these diffs to output a MAJOR, MINOR, or PATCH bump decision with a brief justification.

What is the difference between major, minor, and patch version bumps?▼

A major version bump indicates breaking changes, a minor bump represents new features, and a patch bump signifies bug fixes. Semantic versioning rules categorize these commits and diffs to ensure releases accurately reflect API impact.

How do I automate release planning when evaluating commits and diffs?▼

You can automate release planning by applying semantic versioning rules to your commits and diffs. This skill guides teams through evaluating compatibility constraints to document the appropriate version bump for upcoming releases.

Can I use semantic versioning rules for software release planning without manual diff checking?▼

Yes, you can evaluate changes since the last release automatically. This skill considers breaking changes, new features, and bug fixes across your commits to output a recommended semantic version bump and rationale without manual diff checking.

Does the version bump decision include a justification for the version tag?▼

Yes, the version bump decision includes a brief justification. It considers breaking changes, new features, and bug fixes across your diffs to return the bump decision in MAJOR.MINOR.PATCH format along with the rationale.

Related Skills

Explore More Software Engineering Skills→
lidge-junlidge-jun
5

changelog-generator

Generate user-facing changelogs from git commit history.

Community
Intermediate
joshftjoshft
65

crelease

Determine version bumps, generate changelogs, and create annotated git tags.

Community
Advanced
Edison-WatchEdison-Watch
2

version-bump-reminder

Analyze GitHub pull requests and commits to recommend semantic version bumps.

Official
Intermediate
olga-mirolga-mir
1

conventional-commits

Generate commit messages conforming to the Conventional Commits specification.

Community
Advanced