← ClaudeAtlas

releaselisted

Cut a release properly: work out the version from what actually landed, derive the change set from the commit range, check for blockers, write notes someone would want to read, and drive the release out. Use it whenever a version is about to move — "cut a release", "ship 0.19", "tag a new version", "publish the new version", "bump the version", "write the changelog", "what's changed since the last release?", "is this ready to release?". Do NOT do any of it by hand instead: hand-tagging, editing a version string directly, writing notes off `git log`, or calling `gh release create` yourself skips the blocker check and gets the contents wrong, because a search for merged pull requests returns work the release does not contain and only the commit range is correct. This is releasing a version, not merging a change — shipping one piece of work is `/work-on`.
tsukumogami/shirabe · ★ 0 · Code & Development · score 67
Install: claude install-skill tsukumogami/shirabe
!`bash ${CLAUDE_PLUGIN_ROOT}/scripts/skill-preflight.sh release 2>&1 || true` # Release Cut a release. Handles version selection, precondition checks, blocker identification, release notes, draft creation, workflow dispatch, and monitoring. ## Invocation ``` /release [version] [--dry-run] ``` - **`/release`** -- analyzes commits and recommends a version - **`/release 0.3.0`** -- uses the specified version (`v0.3.0` also accepted) - **`/release --dry-run`** -- previews without side effects ## Phases ### Phase 1: Version Analysis and Release Contents Establish what the release contains, once. Phase 2's security check and Phase 3's notes are both consumers of the pull request set derived here; neither re-derives it. ```bash LAST_TAG=$(git describe --tags --abbrev=0 --match 'v*' 2>/dev/null || echo "") # The commit range the release covers. An empty LAST_TAG is the first release. # The guard is load-bearing: "..HEAD" is a range git ACCEPTS, and it resolves to # zero commits, so without it a first release derives an empty set silently # rather than failing. if [ -n "$LAST_TAG" ]; then RELEASE_RANGE="$LAST_TAG..HEAD" else RELEASE_RANGE="HEAD" fi # Later phases run as separate shell invocations, so the derivation is written # to files rather than left in variables: a shell variable set here is gone by # the time Phase 2 runs, and an empty list there would pass the security check # by finding nothing. These three files ARE the release's membership. mkdir -p wip printf