skills.rest
CruxExperts
CruxExpertsCOMMUNITY
Explore all skills by this author →
WebsiteGitHub

ls-automatic-versioning

Derive MAJOR.MINOR.PATCH versions from conventional commits and synchronize docs.

3|2|Updated Dec 25, 2025
Search Tags:#versioning#release-management#semantic-versioning#conventional-commits#docs-sync#git-workflows
One-click install
npx skills add https://github.com/CruxExperts/localsetup --skill ls-automatic-versioning
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: ls-automatic-versioning
Source: https://github.com/CruxExperts/localsetup/tree/main/_localsetup/skills/ls-automatic-versioning
Command: npx skills add https://github.com/CruxExperts/localsetup --skill ls-automatic-versioning

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Versioning drift across a repo and its docs makes releases uncertain; this framework enforces a single source of truth for version numbers.

Core Features & Use Cases

  • Derives and enforces MAJOR.MINOR.PATCH from conventional commits.
  • Synchronizes the README/framework docs with the canonical VERSION value.
  • Use Case: When preparing a release, ensure all docs reflect the correct version automatically.

Quick Start

Run the release workflow to bump the version according to conventional commits and synchronize docs.

Frequently Asked Questions about ls-automatic-versioning

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

FAQPage Schema
How do I keep version numbers consistent across my repository docs and code?▼

Semantic versioning prevents versioning drift by using a canonical VERSION file as the single source of truth. It synchronizes README and framework docs with the canonical value, ensuring all repository files reflect the correct release automatically.

How do I automatically bump MAJOR.MINOR.PATCH versions from conventional commits?▼

You can derive MAJOR.MINOR.PATCH bumps automatically by parsing conventional commit messages. The release workflow reads commit history, calculates the appropriate semantic version increment, and updates the canonical VERSION file accordingly.

What is the best way to synchronize README documentation with the current release version?▼

Documentation synchronization aligns README and framework docs with the canonical VERSION value. Running the release workflow automatically updates front-matter and tooling references to match the single source of truth, preventing manual update errors.

Does this versioning approach work without external dependencies or specific components?▼

Yes, this versioning framework operates with no external dependencies or components. It relies solely on your repository's conventional commit history and a VERSION file to enforce version governance across git workflows.

Why does versioning drift happen in release management and how can I prevent it?▼

Versioning drift occurs when documentation and code maintain separate version numbers. Prevent drift by enforcing a single source of truth where a canonical VERSION file dictates the MAJOR.MINOR.PATCH values across all repository workflows and audit trails.

Related Skills

Explore More Software Engineering Skills→
cptnfrencptnfren
3

localsetup-automatic-versioning

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

Community
Advanced
pzheng460pzheng460

release

Prepare version bumps, update changelogs, and push annotated git tags.

Community
Intermediate
avvaleavvale

conventional-commits

Validate commit messages against the Conventional Commits specification.

Official
Basic
no-problem-devno-problem-dev
5

release-prepare

Update CHANGELOG, validate semantic versioning, and push release branches via Git.

Official
Intermediate