faq-collector
将成功解决的用户问题收录到 FAQ 知识库。问题解决后自动判断是否收录。也可以在用户说"收录到 FAQ"、"记录这个问题"、"add to FAQ"时手动触发。
git clone --depth 1 https://github.com/CherryHQ/cherry-studio /tmp/faq-collector && cp -r /tmp/faq-collector/resources/builtin-agents/cherry-assistant/.claude/skills/faq-collector ~/.claude/skills/faq-collectorSKILL.md
# FAQ Collector **收录标准**: 通用性高、有明确方案、配置/操作类、非直觉问题。不收录: 纯个人环境问题、已有相同条目、未解决问题。 **文件**: `<project_root>/.cherry-assistant/faq.md`(目录不存在则 `mkdir -p .cherry-assistant` 创建) **条目格式**(追加到末尾): ```markdown ### Q: [通用化问题表述] **A:** [简洁方案] [分步骤操作] - **关键词**: [逗号分隔] - **相关文件/Issue**: [路径或#编号] - **版本**: vX.X.X | **收录日期**: YYYY-MM-DD --- ``` **流程**: 问题解决→判断收录标准→读FAQ查重→无重复则通用化后追加→有相似但更好则更新 **搜索匹配**: 用户提问时先读FAQ关键词匹配→命中直接给答案→未命中走正常诊断 **与 Issue Reporter 协作**: 先收录FAQ(记录方案)→如果是Bug再提Issue→FAQ记关联Issue编号
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、当前版本,或报告运行错误、连接失败、配置异常并需要诊断时触发。