← ClaudeAtlas

patchlisted

Cut a patch release (X.Y.Z to X.Y.Z+1) of the current git repo, committed as "vX.Y.Z - Summary", tagged, and pushed.
jmusick/skills · ★ 0 · AI & Automation · score 65
Install: claude install-skill jmusick/skills
# Patch release Ship the work in this repo as the next **patch** version: `X.Y.Z` becomes `X.Y.(Z+1)`. Typing the command is the go-ahead to commit, tag, and push, so don't confirm along the way. Convention: one commit holds the session's work and the version bump, subject `vX.Y.Z - <summary>` (e.g. `v1.20.5 - Secure staff story previews`), tagged `vX.Y.Z`. ## 1. Survey the repo Fetch first, so the survey compares against what's on the remote now, then run the read-only script from anywhere inside the repo (`python3` if `python` isn't found): ```bash git fetch origin --tags python <this skill's directory>/scripts/version_info.py patch ``` It prints JSON: current and next version, latest tag and `tag_style`, whether origin already has the next tag or a newer one, version files with `in_lockstep`, changelog path and whether it has an `Unreleased` section, branch and upstream, uncommitted changes, and commits since the tag. If it can't run, gather the same from git and the project's version files. Skim `AGENTS.md` / `CLAUDE.md` for a release section; follow any project-specific steps. If `versions_disagree` is true, see "When to stop and ask". ## 2. Understand what's being released The release covers everything since the last tag. Combine the conversation (intent) with `git diff`, `git diff --staged`, and `git log <tag>..HEAD` (what changed). Everything gets staged, so check the tree for `.env` files, credentials, large build output, debug junk, or unrelated changes, an