Skip to content

skillGit and releases

Release Checklist

Runs a release step by step: verifies the branch, tests and changelog, tags the version, builds artifacts and writes a rollback note before shipping.

npx workspacetemplates add release-checklist --tool claude-code

Writes 1 file to .claude/skills/release-checklist/

.claude/skills/release-checklist/SKILL.md28 lines · 1.7 KBFile
---
name: release-checklist
description: "Runs a release step by step: verifies the branch, tests and changelog, tags the version, builds artifacts and writes a rollback note before shipping."
---

# Release checklist

Work the gates in order. A failed gate stops the release.

## Gates

1. **Branch**: on the release branch, `git status` clean, up to date with its remote (`git fetch` then compare). Nothing unmerged that should be in.
2. **CI**: the latest run for this exact commit passed. If you cannot see CI, run the full local suite: lint, typecheck, tests, build.
3. **Version**: decide it from the changes (major for breaking), update every file that holds it, and confirm they agree.
4. **Changelog**: an entry for this version with date, grouped as Added, Changed, Fixed, Removed, each item written for a user. Breaking changes get a migration line.
5. **Dependencies and security**: run the audit command for the ecosystem (`npm audit --omit=dev`, `pip-audit`, `cargo audit`); list anything high or critical.
6. **Artifacts**: build from a clean checkout, record file names and sizes, and run a smoke test of the built output (import it, start it, hit the health endpoint).
7. **Tag**: annotated, on the release commit: `git tag -a vX.Y.Z -m "..."`. Verify with `git show vX.Y.Z --stat`.
8. **Rollback note**: write down the previous version, the exact command to deploy or reinstall it, any database migration that is not reversible, and who to tell.

## Rules

- Do not push tags, publish packages or deploy until the user says "ship it" after seeing the summary.
- Never skip a gate silently. A skipped gate is listed with the reason.

## Report

A table of gate, status and evidence, then the rollback note, then the exact commands left for the user to run.

What it does

Releases go wrong in boring ways: a dirty tree, a stale changelog, a tag on the wrong commit, no way back. This skill turns the release into a short checklist that is checked with commands, not remembered.

It stops at the first failed gate and never publishes without your go-ahead. The last output is a rollback note you can follow at two in the morning.

Example

you › Prepare release 1.8.0 of the CLI

agent › 7 of 8 gates pass. Failed: audit found 1 high advisory in `minimist` (transitive, fix in 1.2.8; updated and re-tested). Tagged v1.8.0 locally. Built 3 artifacts (linux, mac, win; 9.1 to 11.4 MB) and ran `--version` on each. Rollback note written: reinstall 1.7.2, no schema changes. Waiting for your go-ahead to push the tag.

Questions

Does it publish for me?
No. It prepares everything and prints the final commands. Publishing, pushing tags and deploying wait for your explicit approval.
Can I change the gates?
Yes. Edit the list in the skill file: remove the ones that do not apply, such as artifacts for a web service, and add your own.
  • Git Bisect Regression

    SkillGit and releases

    Free
  • Git Conflict Resolution

    SkillGit and releases

    Free
  • Git History Cleanup

    SkillGit and releases

    Free
  • Monorepo Management

    Skilltypescript

    Free