agentleFS
Sign inStart free
e-reitbauere-reitbauer/habits/skills/versioning/SKILL.md

versioning

Skill1 starsChanged 6 days agoMITView on GitHub

Use when deciding a version number: bumping a version, cutting a release, tagging, writing a changelog entry, setting up versioning for a project, or when asked which versioning scheme to use (SemVer, CalVer, build numbers). Detects the project's scheme and picks the next version correctly.

  • Commits and pushes

10 other projects use a version of this.

Adopted by

Most recently taken up by

Used with

Projects with it also use security.

Other files people use alongside this one.

Files found in the same public projects as a version of this one, more often than they turn up anywhere else. Each project counts once, large collections count for less, and this file's own repository is left out.
  • 0xSeroSkill

    security

    Also in 3 projects that use this

The file

We split this skill into the rules it gives an agent

3 rules. 0 are common, 2 are distinctive, and 1 is very specific to this project.

  • 0

    Common

    Most of the 10 edited versions we read keep these.

  • 2

    Distinctive

    This author's own choices. Worth a look.

  • 1

    Very specific

    Tied to their project's names, files or tools. Probably skip.

  • Common
  • Distinctive
  • Very specific
  1. Distinctive:

    Follow what the project already does.

    line 13
  2. Distinctive:

    When setting up a new project, recommend SemVer for anything with consumers and CalVer for scheduled apps, and say why.

    line 29
  3. Very specific:

    only docs, chore, ci, test, style, refactor: no release needed

    line 37

“Common” is measured: kept by at least 6 in 10 of the 10 edited versions of this file we could read. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
SKILL.md

Versioning

1. Detect the scheme in use

Follow what the project already does; never switch schemes as a side effect.

  • Tags: git tag --sort=-creatordate | head. Note the format (v1.2.3, 1.2.3, 2026.11.0, app-v1.2.3 per package).
  • Version sources: package.json, gradle.properties / build.gradle(.kts), pom.xml, Cargo.toml, pyproject.toml, .claude-plugin/plugin.json, Xcode MARKETING_VERSION / CURRENT_PROJECT_VERSION, Android versionName / versionCode.
  • Release tooling owns the number when present: release-please, semantic-release, changesets. Then you don't edit versions by hand; you write the commits or changesets that drive them.
  • CHANGELOG.md: keep its existing format (Keep a Changelog or the tool's generated style).

2. The schemes, and when each fits

SchemeShapeFits
SemVerMAJOR.MINOR.PATCHlibraries, CLIs, plugins, APIs: anything others depend on
CalVerYYYY.MM.MICRO or YY.MMapps and services released on a schedule, where "how new" matters more than compatibility
Build numbersan always-increasing integerstore builds: Android versionCode, iOS CURRENT_PROJECT_VERSION, next to a user-facing SemVer or CalVer
Unversionedcommit SHAcontinuously deployed sites and services with no consumers of a version

When setting up a new project, recommend SemVer for anything with consumers and CalVer for scheduled apps, and say why.

3. Picking the next SemVer version

From the Conventional Commits since the last tag (git log <last-tag>..HEAD --oneline):

  • any ! or BREAKING CHANGE footer: MAJOR (before 1.0.0, bump MINOR instead)
  • any feat: MINOR
  • otherwise any fix or perf: PATCH
  • only docs, chore, ci, test, style, refactor: no release needed

Breaking means a consumer has to change something: removed or renamed public API, changed behaviour they rely on, raised minimum runtime or platform. Internal refactors are never breaking.

Pre-releases: 1.3.0-rc.1, 1.3.0-beta.2, ordered and incremented within their label; the final release drops the suffix. 0.x signals an unstable API; move to 1.0.0 when the API is something you commit to.

4. Rules

  • One version, one meaning: never re-tag or move a published tag, and never reuse a version number. A broken release gets a new patch.
  • Bump every place that holds the version in the same commit (manifest, lockfile entries, plugin.json, app version files), conventionally chore(release): x.y.z.
  • Mobile: increase the build number for every store upload, even when the user-facing version stays the same.
  • Monorepos: either one version for everything (fixed) or per-package versions (independent, with per-package tags like pkg@1.2.3). Follow the project's choice; changesets and release-please both support either.
  • Tag after the release commit is on the release branch, and push tags explicitly (git push origin <tag>) only with the user's go-ahead.
  • Changelog entries describe what changed for users, grouped by Added / Changed / Fixed / Removed, newest first.

Download now (ZIP)

Does it work?

Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.

No reviews yet

People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.

  • It worked
  • Partly
  • It didn't
What did you use it for? e.g. Reviewing pull requests in a Rails app

Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.

Your trail

Files you open will collect here, so you can find them again.

Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.

Now do this for your own.

Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.

Check your setup, free