skills.rest
jayteealao
jayteealaoCOMMUNITY
Explore all skills by this author →
GitHub

version-bump

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

Updated Dec 29, 2025
Search Tags:#git#release-management#ci-cd#semantic-versioning#conventional-commits#version-bump#multi-file-sync
One-click install
npx skills add https://github.com/jayteealao/Aperture --skill version-bump-jayteealao
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: version-bump
Source: https://github.com/jayteealao/Aperture/tree/main/.claude/skills/version-bump
Command: npx skills add https://github.com/jayteealao/Aperture --skill version-bump-jayteealao

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill automates the process of determining semantic version bumps for any project by inspecting version files and commit history, ensuring consistent releases.

Core Features & Use Cases

  • Multi-format version detection: reads version from package.json, pyproject.toml, Cargo.toml, and other adapters.
  • Commit-based bump analysis: supports conventional commits to derive major/minor/patch.
  • Multi-file syncing: validates and updates multiple version files in a single release.
  • Use Case: teams with monorepos or multi-language repos can keep all version files in sync automatically.

Quick Start

Run the release workflow to calculate the next version based on your repository history and commit messages.

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 using conventional commits?▼

You can automate semantic version bumps by analyzing Git commit history for conventional commit prefixes to calculate major, minor, or patch increments and propose a new version with clear rationale.

Can I sync version files across multiple languages in a monorepo?▼

Yes, multi-file syncing validates and updates version files like package.json, pyproject.toml, and Cargo.toml simultaneously, keeping all version declarations synchronized across multi-language repositories.

What's the best way to determine the next release version from Git history?▼

The best way to determine the next release version is by reading existing version files and analyzing commit history to derive the appropriate semantic version bump based on conventional commit messages.

Does this version bump tool support Python and Rust project formats?▼

Yes, the version bump tool supports Python and Rust projects by reading version metadata directly from pyproject.toml and Cargo.toml files alongside other compatible language adapters.

How does conventional commit analysis decide between major and minor bumps?▼

Conventional commit analysis decides major, minor, or patch bumps by parsing commit message prefixes like feat or breaking change, mapping them to semantic versioning rules to calculate the next version.

Why do I need automated version bumping for CI/CD release management?▼

Automated version bumping ensures consistent releases by inspecting version files and commit history, eliminating human error in manual version calculations and keeping multi-file version declarations synchronized during CI/CD workflows.

Related Skills

Explore More Software Engineering Skills→
bingeli1379bingeli1379
2

release

Detect current version, generate a Keep a Changelog entry, and bump version files.

Community
Advanced
krodakkrodak
102

releasing-clickup-cli

Automate npm publish, Homebrew tap updates, and agent skill sync for clickup-cli releases.

Community
Advanced
voidrotvoidrot

changelog-automation

Generate changelogs and release notes from commit history and tags.

Community
Advanced
pradyumnasagarpradyumnasagar
6

release-management

Manages ORS skill releases with versioning, changelogs, and marketplace updates.

Community
Intermediate