Prepare a new release by collecting commits, generating bilingual release notes, updating version files, and creating a release branch with PR. Use when asked to prepare/create a release, bump version, or run `/prepare-release`.
Prepare Release Automate the Cherry Studio release workflow: collect changes → generate bilingual release notes → update files → create release branch + PR → trigger CI/CD. Arguments Parse the version intent from the user's message. Accept any of these forms: Bump type keyword: , , Exact version: or (e.g. , , ) Natural language: "prepare a beta release", "bump to 1.8.0 rc.2", etc. Defaults to if no version is specified. Always echo the resolved target version back to the user before proceeding…
Full body not shown for this license – view the source on GitHub →Copy a source-pinned command for your client. You run it yourself.
Destination: .claude/skills/prepare-release · pinned to the source commit
git clone https://github.com/CherryHQ/cherry-studio.git
cd cherry-studio
git checkout 18c287b020ff95cc2a12fc389ea4748957fbaf49
mkdir -p ".claude/skills/prepare-release"
cp -r ".agents/skills/prepare-release" ".claude/skills/prepare-release"Review the source before running. This copies files into your project; it is not a one-click install and does not verify runtime safety.
Scanner static-checks@0.1.0 · commit 18c287b020ff. Static checks cannot prove runtime safety – review the source and the exact diff before installing. How checks work.
No static rules matched. This is not a safety guarantee.