version

Name: version
Availability: InStock
Author: bismuthdigital

Analyzes code changes to update semantic version files and create Git tags.

Updated Feb 1, 2026

Search Tags:#automation #git #release management #versioning #semantic versioning #tagging

Ready to run

npx skills add https://github.com/bismuthdigital/claude-project-template --skill version-bismuthdigital

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: version
Source: https://github.com/bismuthdigital/claude-project-template/tree/main/.claude/skills/version
Command: npx skills add https://github.com/bismuthdigital/claude-project-template --skill version-bismuthdigital

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) and references (resource) components.

What problem does it solve?

This Skill automates the process of managing semantic versioning for your project, ensuring consistency and reducing manual errors in version updates and Git tagging.

Core Features & Use Cases

Automated Version Bumping: Analyzes code changes to suggest or automatically apply major, minor, or patch version increments.
Version File Updates: Modifies version numbers in specified project files (e.g., pyproject.toml, __init__.py).
Git Tagging: Creates annotated Git tags for new releases and pushes them to the remote repository.
Use Case: After merging a new feature branch, run /version to automatically determine if a minor version bump is needed, update all version files, commit the change, and create a vX.Y.Z tag.

Quick Start

Run the version skill to automatically detect the next version increment and create a git tag.

Frequently Asked Questions about version

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

FAQPage Schema

How do I automate semantic versioning and Git tagging for my project?▼

Automate semantic versioning by analyzing code changes and parsing conventional commit messages to determine version increments. The process updates version files like pyproject.toml, commits the change, and creates annotated Git tags for automated release management.

How does conventional commit parsing work for automated version bumping?▼

Conventional commit parsing works by analyzing commit messages to detect specific patterns that dictate semantic versioning increments. It identifies whether code changes require a major, minor, or patch version bump, ensuring version updates align with development standards.

Can I use this to update version numbers across multiple project files?▼

Yes, you can update version numbers across multiple project files. The process modifies specified files such as pyproject.toml and __init__.py, ensuring all version declarations within the software project remain synchronized during the release management workflow.

Do I need Git command-line tools to manage semantic versioning this way?▼

Yes, Git command-line tools are required to manage semantic versioning this way. The workflow depends on Git operations to parse repository history, commit updated version files, create annotated release tags, and push those tags to the remote repository.

What is the best way to create annotated Git tags for software releases?▼

The best way to create annotated Git tags for releases is through an automated semantic versioning workflow. After determining the correct version increment from code changes, the system automatically creates the annotated tag and pushes it to your remote repository.

Why does automated release management require parsing commit messages?▼

Automated release management requires parsing commit messages to understand the context of recent code changes. By detecting conventional commit patterns, the system determines whether changes represent breaking changes, new features, or simple patches to calculate the correct semantic version bump.