solo: Skill for Claude Code

Solo Prepare Release

Prepare the documentation and branch for a new Solo release. This skill encodes the exact steps the Solo team follows so the README release table, the legacy table, and the version math stay consistent.

Run everything from the solo/ repo root (the directory containing version.ts, README.md, and legacy-versions.md). Verify with git rev-parse --show-toplevel before starting.

When to use

• The user asks to prepare/cut a release, bump the version, or open a release PR for Solo.

Do not use for: actually tagging/publishing the release (that is the release workflow, not this skill), or for non-Solo repos.

Inputs to gather first

Fact	How to get it
Last released version	git describe --tags --abbrev=0 (e.g. v0.79.0)
Commits since last tag	git log "$(git describe --tags --abbrev=0)"..HEAD --pretty=%s
Today's date	date +%Y-%m-%d
Dependency versions	version.ts constants (see mapping below)

Step 1 — Determine the next version

Read the current version from package.json ("version") — confirm it matches the last tag.

Decide the bump by inspecting commit subjects since the last tag:

LAST_TAG="$(git describe --tags --abbrev=0)"
git log "${LAST_TAG}..HEAD" --pretty=%s

• If any subject starts with feat: (also count conventional variants feat(scope): and feat!:/feat(scope)!:), bump the minor version and reset patch to 0 → 0.79.0 becomes 0.80.0.
• Otherwise bump only the patch version → 0.79.0 becomes 0.79.1.

Detection one-liner (NEXT ends up as the bare version, no leading v):

CUR="$(node -p "require('./package.json').version")"   # e.g. 0.79.0
IFS=. read -r MAJ MIN PAT <<< "${CUR}"
if git log "${LAST_TAG}..HEAD" --pretty=%s | grep -Eq '^feat(\(.+\))?!?:'; then
  NEXT="${MAJ}.$((MIN + 1)).0"
else
  NEXT="${MAJ}.${MIN}.$((PAT + 1))"
fi
echo "Next version: ${NEXT}"

State the computed version and the reason (feat found → minor / none → patch) before proceeding.