skills.rest
Xantibody
XantibodyCOMMUNITY
Explore all skills by this author →
GitHub

version

Determine the next Semantic Versioning number from Conventional Commits history.

1|Updated Dec 12, 2024
Search Tags:#git#release management#versioning#conventional commits#semantic versioning#semver
One-click install
npx skills add https://github.com/Xantibody/dotfiles --skill version-xantibody
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: version
Source: https://github.com/Xantibody/dotfiles/tree/main/configs/claude/skills/version
Command: npx skills add https://github.com/Xantibody/dotfiles --skill version-xantibody

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This Skill automates the process of determining the next version number for software releases, ensuring adherence to Semantic Versioning standards and simplifying release management.

Core Features & Use Cases

  • Semantic Versioning: Calculates the next MAJOR, MINOR, or PATCH version based on commit history.
  • Conventional Commits Analysis: Analyzes commit messages for feat, fix, BREAKING CHANGE, and other indicators to recommend the appropriate version bump.
  • Use Case: Before creating a new release tag, use this skill to analyze recent commits and get a clear recommendation for the next version number (e.g., 1.2.3 -> 1.3.0).

Quick Start

Use the version skill to determine the next version based on the commit history.

Frequently Asked Questions about version

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

FAQPage Schema
How do I determine the next semantic version from git commit history?▼

Semantic versioning calculates version bumps as MAJOR, MINOR, or PATCH. It uses Conventional Commits to analyze git history, identifying feat, fix, or BREAKING CHANGE to recommend the next release number.

What's the best way to automate release management and versioning?▼

Automating release management involves calculating the next software version number following Semantic Versioning 2.0.0 rules based on commit history, simplifying the preparation of release tags.

How does conventional commits analysis recommend a PATCH or MINOR version bump?▼

Conventional commits analysis scans git commit messages for specific keywords. A feat triggers a MINOR bump, while a fix triggers a PATCH bump, ensuring the semantic version reflects the changes.

Can I identify pre-release and build metadata when calculating the next version?▼

Yes, you can identify pre-release and build metadata during version calculation. The process supports these identifiers to provide a clear recommendation for release preparation.

Does this semantic versioning approach work without external dependencies?▼

Yes, this semantic versioning approach works without external dependencies. It directly analyzes commit history using Conventional Commits to recommend the next version number.

Related Skills

Explore More Software Engineering Skills→
t0labt0lab
2

git-conventional

Enforce Conventional Commits formatting and map commit types to semantic version bumps.

Official
Basic
thoreinsteinthoreinstein
10

release

Automate release notes, changelogs, and signed git tags.

Community
Advanced
CommunityToolkitCommunityToolkit
619

release-process

Automates npm release validation, publishing procedures, and post-publish verification for software workflows.

Official
Intermediate
jayteealaojayteealao

version-bump

Automates semantic-version bump calculation from Git commit history and version files.

Community
Advanced