How do I install the Localsetup Automatic Versioning skill?

Run npx skillmds add majiayu000/localsetup-automatic-versioning in your terminal (requires Node.js), paste this page's agent-chat prompt into Claude, Cursor, or any MCP-connected agent, or download the SKILL.md file and copy it into your agent's skills directory.

Is Localsetup Automatic Versioning safe to use?

This skill has not completed SkillMD's automated safety review yet. Capability flags: docs only. SkillMD never runs a skill's scripts for you; review the SKILL.md before installing.

Which AI agents work with Localsetup Automatic Versioning?

This skill is tagged as working with Claude Code, Claude.ai, OpenAI Codex. SKILL.md is an open format, so most agents that read a skills directory can load it too.

Is Localsetup Automatic Versioning free to use?

Yes. Installing skills from SkillMD is free, and the skill stays under its author's original license.

Who published Localsetup Automatic Versioning?

majiayu000 (@majiayu000) published this skill. Their other Agent Skills are listed on their SkillMD profile.

Localsetup Automatic Versioning by majiayu000

Name: Localsetup Automatic Versioning
Rating: 4.2 (5 reviews)
Author: majiayu000

Localsetup Automatic Versioning

Use and maintain automatic versioning from conventional commits; VERSION as source of truth; sync to READMEs and docs. Use when working on version bumps, release workflow, or when the user asks about versioning or conventional commits.

majiayu000 5aab69d 2 files · 2.6 KB Updated Sep 9, 2026 567 repo stars

File contents

Automatic versioning (framework)

Purpose: The framework uses semantic versioning with VERSION as source of truth. Use this skill when implementing, explaining, or changing versioning behavior so it stays consistent and framework-appropriate.

Source of truth

VERSION (repo root): single line, semantic version MAJOR.MINOR.PATCH (e.g. 2.0.0). This is the only canonical version value.
Displayed version must stay in sync: README and framework README show **Version:** X.Y.Z; framework docs use YAML front matter version: X.Y (major.minor). The repository maintainers keep these in sync when they run the publish workflow.

Conventional Commits → bump type

MAJOR: BREAKING CHANGE: in body, or type followed by ! (e.g. feat!: new API).
MINOR: feat: (new feature).
PATCH: fix:, docs:, chore:, style:, refactor:, perf:, test:, ci:, build:; any other message defaults to PATCH.
No bump: Merge commits (message starts with Merge ).

In this repo (public framework)

Version bump and doc sync are performed by the repository maintainers. Contributors do not need to run any scripts. If you are working in a repo that has the maintainer publish workflow (e.g. the framework maintainer repo), run the publish workflow from that context as documented there.

Reference

Versioning doc: docs/VERSIONING.md (slim) or _localsetup/docs/VERSIONING.md in a deployed copy.

Frequently asked questions