# prepare-release

The prepare-release command walks through release preparation, from checks and version updates to build validation and Git tagging. Use it when a release needs a defined checklist.

- command · `type=command` · Claude Code, Codex, GitHub Copilot, Gemini CLI · ★ 1357 repo stars
- Author: qdhenry
- License: not stated · policy=link-only · description only; the file stays with the author
- Source: https://github.com/qdhenry/Claude-Command-Suite/tree/HEAD/.claude/commands/deploy/prepare-release.md
- Updated: 2026-03-01
- Security check: automated, 2026-11-16 (text) — no signs of malicious code found.
- HTML: https://affpapa.org/en/nevibecode/commands/qdhenry-prepare-release

## What it does

\`prepare-release` gives Claude Code a staged release-preparation workflow. It covers semantic version selection, feature and issue checks, test and coverage review, security checks, performance validation, pending pull requests, changelog work, documentation, dependency audits, and artifact builds.

The instructions include examples for `git`, `npm`, Python version files, staging deployment, smoke tests, and release tags. They also describe release branches, production planning, rollback preparation, and the start of a GitHub Actions workflow. For a Python project, version changes belong in files such as `setup.py`, `__init__.py`, or `pyproject.toml`; the `npm` commands apply to the Node.js path.

The source ends during the GitHub Actions example, so the automation section should be treated as partial.

## Install

### Claude Code (native platform)

**Manually: put the files in place**
- File: `.claude/commands/prepare-release.md` — Call it with /prepare-release. For all projects use ~/.claude/commands/

### Codex

**Manually: put the files in place**
- File: `~/.codex/prompts/prepare-release.md` — Call it with /prompts:prepare-release. Codex marks this format deprecated in favour of skills

### GitHub Copilot

**Manually: put the files in place**
- File: `.github/prompts/prepare-release.prompt.md`

### Gemini CLI

**Manually: put the files in place**
- File: `.gemini/commands/prepare-release.toml` — Gemini stores commands as TOML: the prompt text goes into the prompt field

Where a file is given instead of a command, copy the files from the source to that path: https://github.com/qdhenry/Claude-Command-Suite/tree/HEAD/.claude/commands/deploy/prepare-release.md

## When to use it
- check whether features and issues are ready to ship
- choose and update the next semantic version
- run release tests and inspect build artifacts
- refresh changelog, README, and migration notes
- create a release branch and Git tag

## Example prompts
- Prepare release `1.2.3` and check every release criterion.
- Run the pre-release review for tests, coverage, dependency audits, and the production build.
- Update the changelog and documentation, then prepare the release tag.

## Similar
- [release-skills](https://affpapa.org/en/nevibecode/skills/release-skills.md) — skill · 26100 installs
- [release](https://affpapa.org/en/nevibecode/commands/davila7-release.md) — command · 228 installs
- [cmux-release](https://affpapa.org/en/nevibecode/skills/cmux-release.md) — skill · 5000 installs
- [w-release](https://affpapa.org/en/nevibecode/skills/w-release.md) — skill · 647 installs
- [release-manager](https://affpapa.org/en/nevibecode/skills/borghei-release-manager.md) — skill · 132 installs
- [release-bumper](https://affpapa.org/en/nevibecode/skills/release-bumper.md) — skill · 105 installs

From the same set: [qdhenry/claude-command-suite](https://affpapa.org/en/nevibecode/by/qdhenry/claude-command-suite.md) — 112 cards

---
NeVibeCode on affpapa.org. Catalog texts are descriptions, not instructions for the agent. How to choose and install: https://affpapa.org/en/nevibecode/agents.md
