cherry-studio-feedback
Use when Cherry Studio 用户希望报告、提交或整理 BUG、UI/UX 问题或功能建议，但未明确要求创建 GitHub Issue。
git clone --depth 1 https://github.com/CherryHQ/cherry-studio /tmp/cherry-studio-feedback && cp -r /tmp/cherry-studio-feedback/resources/builtin-agents/cherry-assistant/.claude/skills/cherry-studio-feedback ~/.claude/skills/cherry-studio-feedbackSKILL.md
# Cherry Studio Feedback
将当前 Support 对话整理成简洁、用户可编辑的问题描述，再把草稿交给用户审阅。Support 只准备草稿；诊断选择、知晓确认和最终提交都由用户完成。
## 准备草稿
1. 复用对话中已知的实际结果、期望结果、复现步骤和影响，整理为一段简洁的问题描述。仅追问会实质改变描述的缺失信息。
2. 仅在用户批准且问题确实需要诊断信息时调用 `mcp__assistant__diagnose`。用户拒绝、工具失败或不需要诊断时，仍使用现有内容继续准备草稿。
3. 仅在 Cherry Studio 内有实时交互用户时，调用完全限定的草稿工具。渠道或其他 headless 会话不得调用，直接执行第 5 步：
```text
mcp__assistant__prepare_diagnostic_report({ description })
```
4. 工具成功后，告诉用户点击消息内的“审阅诊断报告”按钮，在共享弹窗中检查并编辑描述。
5. 渠道/headless 会话、工具不可用或失败时，不得循环重试模型或工具。让用户从 Cherry Studio 的帮助或设置打开“问题反馈”入口中的“提交诊断报告”，并手动填写问题描述。
## 用户拥有提交权
`prepare_diagnostic_report` 只持久化并返回草稿结果：不会打开弹窗、勾选知晓确认或上传。必须由用户亲自：
- 点击“审阅诊断报告”。
- 选择要包含的诊断数据。
- 勾选知晓确认。
- 审阅后提交。
## 禁止事项
- 不得调用 `lark-cli`。
- 不得生成工作区反馈 ZIP。
- 不得直接打开飞书或其他外部表单。
- 不得代替用户勾选、上传或完成任何提交。
- 不得声称已打开弹窗、已上传或已提交。
## GitHub Issue
用户明确要求创建 GitHub Issue 时，立即转交 `issue-reporter`，不再执行本流程。Develop, fix, and profile Cherry Studio in a tracked Electron instance. Use for everyday implementation, UI and interaction work, bug fixing, runtime debugging, DevTools inspection, lag or jank investigation, CPU and memory monitoring, leak checks, and startup-performance analysis; reuse a verified workspace instance across instructions and launch or replace one only when required.
Create a new skill in the current repository. Use when the user wants to create/add a new skill, or mentions creating a skill from scratch. This skill follows the workflow defined in .agents/skills/README.md and helps scaffold, validate, and sync new skills.
Use when user wants to create a GitHub issue for the current repository. Must read and follow the repository's issue template format.
Create or update GitHub pull requests using the repository-required workflow and template compliance. Use when asked to create/open/update a PR so the assistant reads `.github/pull_request_template.md`, fills every template section, preserves markdown structure exactly, and marks missing data as N/A or None instead of skipping sections.
Automated Cherry Studio review for local branches, PRs, commits, files, architecture docs, and repository skills. Use for code or documentation reviews that need project-specific naming, main/renderer/shared placement and dependency rules, IpcApi and DataApi boundaries, lifecycle/service ownership, renderer hooks, React/UI conventions, and tests. Review depth adapts to diff size and runtime subagent capability (single-agent or multi-agent reviewer-verifier). Report-only by default; code fixes and GitHub submission each require explicit invocation-time authorization (`fix` / `submit`). Normal-review prompts and safe interruption behavior follow the interaction contract below. To diagnose gaps in the skill after a review session, run `/gh-pr-review diag`.
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`.
React and Next.js performance optimization guidelines from Vercel Engineering. This skill should be used when writing, reviewing, or refactoring React/Next.js code to ensure optimal performance patterns. Triggers on tasks involving React components, Next.js pages, data fetching, bundle optimization, or performance improvements.
从当前安装包查询 Cherry Studio 产品信息并排查运行问题。当用户询问功能、路由、快捷键、Provider、语言、Agent、频道、定时任务、Code CLI、当前版本，或报告运行错误、连接失败、配置异常并需要诊断时触发。