localsetup-automatic-versioning

Name: localsetup-automatic-versioning
Availability: InStock
Author: cptnfren

Automate version bumps from conventional commits and update VERSION, READMEs, and docs.

3|2|Updated Dec 25, 2025

Search Tags:#versioning #documentation #semantic-versioning #conventional-commits #readme-sync #release-workflow

Ready to run

npx skills add https://github.com/cptnfren/localsetup --skill localsetup-automatic-versioning

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: localsetup-automatic-versioning
Source: https://github.com/cptnfren/localsetup/tree/main/_localsetup/skills/localsetup-automatic-versioning
Command: npx skills add https://github.com/cptnfren/localsetup --skill localsetup-automatic-versioning

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Versioning often drifts across code, docs, and releases. This skill enforces semantic versioning with VERSION as the single source of truth and keeps READMEs and docs in sync with the current release level.

Core Features & Use Cases

Semantic Versioning: uses the VERSION file to determine MAJOR, MINOR, and PATCH.
Readme & Docs Sync: updates displayed version in READMEs and documentation to reflect the latest release.
Release Workflow Support: integrates with conventional commits to drive bumps automatically during releases.

Quick Start

Run the versioning process to apply the next bump based on the latest conventional-commit messages and propagate the changes.

Frequently Asked Questions about localsetup-automatic-versioning

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

FAQPage Schema

How do I automate semantic versioning using conventional commits?▼

Automate semantic versioning by interpreting conventional-commit messages to trigger version bumps and propagate those updates to a central VERSION file. This process determines the MAJOR, MINOR, or PATCH increment based on your latest commit history.

How do I keep my README version in sync with my project releases?▼

Keep your README in sync by using a central VERSION file as the single source of truth. The versioning process propagates the current semantic version across your documentation automatically whenever a new release bump occurs.

Do I need a specific commit message format to automate version bumps?▼

Yes, you need a conventional-commit workflow. The version bump logic interprets specific conventional-commit messages to determine the correct semantic version increment and synchronize the VERSION file and documentation.

What's the best way to maintain a single source of truth for project versioning?▼

Maintain a single source of truth by storing your semantic version in a root-level VERSION file. This prevents version drift across code, docs, and releases by automatically propagating updates to READMEs and documentation.

Where should the VERSION file be located for automated semantic versioning?▼

The VERSION file must be located at the root of your repository. The versioning process reads this file to determine the current MAJOR, MINOR, and PATCH levels before applying the next bump and propagating changes to documentation.