CherryHQ

Use when user wants to create a GitHub issue for the current repository. Must read and follow the repository's issue template format.

Recommend Claude Code automations (hooks, subagents, skills, plugins, MCP) and review an existing setup.

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,…

Prepare a new release by collecting commits, generating bilingual release notes, updating version files, and creating a release branch

Create, edit, evaluate, and optimize skills, including benchmarking and description tuning for better triggering.

Run Cherry Studio critical-path system regression tasks through the repository-owned Playwright E2E workflow. Use for full regression, release acceptance, development-branch system validation, or a named cherry-regression-test task on GitHub-hosted macOS and Windows runners.

Create or update GitHub pull requests using the repository-required workflow and template compliance

Create a new skill in the current repository

Use when deciding whether a Cherry Studio change needs an Agent Note, authoring or reviewing a Spec, recording a durable bug-fix decision, moving a note between proposed/implemented/rejected, or checking supersession and stacked Spec approval.

Develop, fix, profile, and test PRs in a tracked Cherry Studio Electron instance. Use for implementation, UI and interaction work, runtime debugging, DevTools inspection, performance analysis, and interactive PR verification with a test report.

Control the user''s visible Agent browser: navigate, click, type, screenshot, debug. Needs the Browser setting.

Drive native apps via Computer Use: open, inspect, type, click, screenshot. Needs OS permissions; respect user stop.