Cherry Studio 自动化发布工具：prepare-release 技能详解与使用指南

prepare-release by cherryhq/cherry-studio

1 周安装量

41,000 GitHub Stars

GitHub

安装命令

npx skills add https://github.com/cherryhq/cherry-studio --skill prepare-release

自动化开发运维工程/构建系统

🇨🇳中文介绍

准备发布

自动化 Cherry Studio 的发布工作流程：收集变更 → 生成双语发布说明 → 更新文件 → 创建发布分支 + PR → 触发 CI/CD。

参数

从用户的消息中解析版本意图。接受以下任何形式：

版本升级类型关键词：patch、minor、major
精确版本号：x.y.z 或 x.y.z-pre.N（例如 1.8.0、1.8.0-beta.1、1.8.0-rc.1）
自然语言："prepare a beta release"、"bump to 1.8.0-rc.2" 等。

如果未指定版本，则默认为 patch。在进行任何文件编辑之前，始终向用户回显解析出的目标版本。

广告位招租

在这里展示您的产品或服务

触达数万 AI 开发者，精准高效

联系我们

相关 Skills

FlyClaw：零登录航班聚合查询工具，Python实现多源航班信息与价格搜索

4,000,000 周安装

Vercel React 最佳实践指南 | 58条Next.js性能优化规则与代码重构

269,400 周安装

agent-browser 浏览器自动化工具 - Vercel Labs 命令行网页操作与测试

147,400 周安装

Azure RBAC 权限管理工具：查找最小角色、创建自定义角色与自动化分配

117,000 周安装

获取最新的标签：
```
git describe --tags --abbrev=0
```
从 package.json 读取当前版本。
根据参数计算新版本：
- patch / minor / major：基于当前标签版本进行升级。
- x.y.z 或 x.y.z-pre.N：在验证其为有效的 semver 后直接使用。

列出自上一个标签以来的所有提交：

git log <last-tag>..HEAD --format="%H %s" --no-merges

对于每个提交，获取完整的正文：
```
git log <hash> -1 --format="%B"
```
从每个提交正文中提取 ````release-note` 代码块内的内容。
从标题中提取约定式提交类型（feat、fix、refactor、perf、docs 等）。
跳过以下提交：
- 标题以 🤖 Daily Auto I18N 开头
- 标题以 Merge 开头
- 标题以 chore(deps) 开头
- 标题以 chore: release 开头
- release-note 块内容为 NONE 的提交

仅包含有内容的类别（省略空类别）。
每个提交在适当的类别中仅显示为一行条目。
如果存在 release-note 字段，则使用它；否则根据提交标题进行总结。
组件标签应简短：[Chat]、[Models]、[Agent]、[MCP]、[Settings]、[Data]、[Build] 等。
中文翻译应自然流畅，而非机器直译。
不要包含提交哈希值或 PR 编号。
省略对用户无影响的纯内部提交（重构、CI、文档）。
在编写前，请阅读 electron-builder.yml 中现有的发布说明作为风格参考。

创建并推送发布分支：

git checkout -b release/v{version}
git add package.json electron-builder.yml
git commit -m "chore: release v{version}"
git push -u origin release/v{version}

使用 gh-create-pr skill 创建 PR。如果该技能工具不可用，请阅读 .agents/skills/gh-create-pr/SKILL.md 并手动遵循其步骤。在 CI（非交互式）模式下，跳过交互式确认步骤，在填写模板后直接创建 PR。
- 使用标题：chore: release v{version}
- 使用基础分支：main
- 填写 PR 模板时，包含：
  - 生成的发布说明（仅英文部分，以提高可读性）。
  - 包含的提交列表。
  - 审核清单：
    - 审核 electron-builder.yml 中生成的发布说明
    - 验证 package.json 中的版本升级
    - CI 通过
    - 合并以触发发布构建
报告 PR URL 和后续步骤。

在修改 electron-builder.yml 之前，始终先读取它以了解当前格式。
切勿修改 package.json 和 electron-builder.yml 以外的文件。
切勿直接推送到 main 分支。
在创建分支/PR 之前，始终向用户展示生成的发布说明（除非在没有交互式用户的 CI 环境中运行）。

🇺🇸English

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: patch, minor, major
Exact version: x.y.z or x.y.z-pre.N (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 branch or PR.

Workflow

Step 1: Determine Version

Get the latest tag:
```
git describe --tags --abbrev=0
```
Read current version from package.json.
Compute the new version based on the argument:
- patch / minor / major: bump from the current tag version.
- x.y.z or x.y.z-pre.N: use as-is after validating it is valid semver.

Step 2: Collect Commits

List all commits since the last tag:

git log <last-tag>..HEAD --format="%H %s" --no-merges

For each commit, get the full body:
```
git log <hash> -1 --format="%B"
```
Extract the content inside ````release-note` code blocks from each commit body.
Extract the conventional commit type from the title (feat, fix, refactor, perf, docs, etc.).
Skip these commits:
- Titles starting with 🤖 Daily Auto I18N

Step 3: Generate Bilingual Release Notes

Using the collected commit information, generate release notes in both English and Chinese.

Format (must match exactly):

<!--LANG:en-->
Cherry Studio {version} - {Brief English Title}

✨ New Features
- [Component] Description

🐛 Bug Fixes
- [Component] Description

💄 Improvements
- [Component] Description

⚡ Performance
- [Component] Description

<!--LANG:zh-CN-->
Cherry Studio {version} - {简短中文标题}

✨ 新功能
- [组件] 描述

🐛 问题修复
- [组件] 描述

💄 改进
- [组件] 描述

⚡ 性能优化
- [组件] 描述
<!--LANG:END-->

Rules:

Only include categories that have entries (omit empty categories).
Each commit appears as exactly ONE line item in the appropriate category.
Use the release-note field if present; otherwise summarize from the commit title.
Component tags should be short: [Chat], [Models], [Agent], [MCP], [Settings], [Data], [Build], etc.
Chinese translations should be natural, not machine-literal.
Do NOT include commit hashes or PR numbers.
Omit purely internal commits (refactor, CI, docs) with no user-facing impact.
Read the existing release notes in electron-builder.yml as a style reference before writing.

Step 4: Update Files

package.json : Update the "version" field to the new version.
electron-builder.yml : Replace the content under releaseInfo.releaseNotes: | with the generated notes. Preserve the 4-space YAML indentation for the block scalar content.

Step 5: Present for Review

Show the user:

The new version number.
The full generated release notes.
A summary of which files were modified.

If --dry-run was specified, stop here.

Otherwise, ask the user to confirm before proceeding to Step 6.

Step 6: Create Branch and PR

Create and push the release branch:

git checkout -b release/v{version}
git add package.json electron-builder.yml
git commit -m "chore: release v{version}"
git push -u origin release/v{version}

Create the PR using the gh-create-pr skill. If the skill tool is unavailable, read .agents/skills/gh-create-pr/SKILL.md and follow it manually. In CI (non-interactive) mode, skip interactive confirmation steps and create the PR directly after filling the template.
- Use title: chore: release v{version}
- Use base branch: main
- When filling the PR template, incorporate:
  - The generated release notes (English section only, for readability).
  - A list of included commits.
  - A review checklist:
    - Review generated release notes in electron-builder.yml

CI Trigger Chain

Creating a PR from release/v* to main automatically triggers:

release.yml : Builds on macOS, Windows, Linux and creates a draft GitHub Release.
ci.yml : Runs lint, typecheck, and tests.

Constraints

Always read electron-builder.yml before modifying it to understand the current format.
Never modify files other than package.json and electron-builder.yml.
Never push directly to main.
Always show the generated release notes to the user before creating the branch/PR (unless running in CI with no interactive user).

Weekly Installs

Repository

cherryhq/cherry-studio

GitHub Stars

41.0K

First Seen

5 days ago

Security Audits

Gen Agent Trust HubPass SocketPass SnykPass

Installed on

mcpjam1

github-copilot1

junie1

windsurf1

zencoder1

crush1

Cherry Studio 自动化发布工具：prepare-release 技能详解与使用指南

🇨🇳中文介绍

准备发布

参数

相关 Skills

工作流程

步骤 1：确定版本

步骤 2：收集提交记录

步骤 3：生成双语发布说明

步骤 4：更新文件

步骤 5：提交审核

步骤 6：创建分支和 PR

CI 触发链

约束