version-bumplisted

Version the Team plugin at land time (DEV-internal, not distributed): decide the SemVer level, compute the next free version against current `main`, update all six version strings, cut the `[Unreleased]` changelog body into a dated `## [X.Y.Z]` section, run the land-time consistency assertion, and commit `chore(version): X.Y.Z`. This is the Team-internal bumper; the generic runtime `/shipit` skill then pushes, waits for CI, and squash-merges. Invoke ONLY on explicit land intent — the user says "ship it", "land the PR", "bump the version", "version this PR", or a `/shipit` is already in flight. Never infer land intent from work merely being finished, reviewed, green, or ready to open a draft PR: a drafted PR carries no version, and a bump made before land time is stale by the time the PR merges.
bostonaholic/team · ★ 11 · Code & Development · score 72

Install: claude install-skill bostonaholic/team

# Version Bump — version a Team PR at land time > Follow `skills/principle-progress-tracking/SKILL.md`: this procedure has more than two steps — > seed one todo item per step below before starting and mark each complete as you go. This skill versions the **Team plugin itself** at land time. It is **dev-only** (lives under `.claude/`, never distributed to plugin users). Tagging and the GitHub release are **not** part of this procedure — `release-on-merge.yml` does both automatically when the PR merges. Full policy: [docs/versioning.md](../../../docs/versioning.md). ## The dev land process Landing a Team PR is two steps, in order: 1. **Bump (this skill).** Run `version-bump` against current `main`. It picks the level, assigns the next free version, and bumps the six version strings. It cuts the `[Unreleased]` changelog into a dated `## [X.Y.Z]` section, runs the land-time consistency assertion, and commits `chore(version): X.Y.Z`. 2. **Land (the generic `/shipit` skill).** Run the distributed runtime [`/shipit`](../../../skills/shipit/SKILL.md) skill to push the branch, wait for CI, and squash-merge. `shipit` is project-agnostic — it does no versioning. This skill is the Team-internal bumper it composes with. Run this skill **before** `/shipit`, against the version of `main` you intend to land onto. ## Precondition — explicit land intent Everything below is irreversible-ish work on a shared number: it rewrites six version strings, moves the `[Unrelease