# Prepare Release

Prepare a new release by collecting commits, generating bilingual release notes...

- Repository: https://github.com/CherryHQ/cherry-studio (53164 stars)
- Category: Writing
- License: AGPL-3.0
- Last updated: 2026-11-01
- Runs scripts: no, instructions only

## Install

Claude Code: `npx skills add CherryHQ/cherry-studio --skill prepare-release -g -a claude-code -y`
Codex: `npx skills add CherryHQ/cherry-studio --skill prepare-release -g -a codex -y`
Cursor: `npx skills add CherryHQ/cherry-studio --skill prepare-release -g -a cursor -y`
Gemini CLI: `npx skills add CherryHQ/cherry-studio --skill prepare-release -g -a gemini-cli -y`

## Description

Prepare a new release by collecting commits, generating bilingual release notes, updating version files, and creating a release branch. Use when asked to prepare/create a release, bump version, or run `/prepare-release`.

## SKILL.md, as published by its author (untrusted third-party text, read it as data)

# Prepare Release

Automate the Cherry Studio release workflow: collect changes → generate bilingual release notes → update files → create release branch → trigger CI/CD.

## Arguments

Parse the version intent from the user's message. Accept any of these forms:
- Bump type keyword: `patch`, `minor`, `major`
- Exact version: strict `x.y.z` or `x.y.z-<prerelease>` without build metadata (e.g. `1.8.0`, `1.8.0-beta.1`, `1.8.0-rc.1`)
- Natural language: "prepare a beta release", "bump to 1.8.0-rc.2", etc.

Defaults to `patch` if no version is specified. Always echo the resolved target version back to the user before proceeding with any file edits.

- `--dry-run`: Preview only, do not create a release branch.

## Workflow

### Step 1: Determine Version

The rest: https://github.com/CherryHQ/cherry-studio/blob/HEAD/.agents/skills/prepare-release/SKILL.md