cherry-pr-test
Test Cherry Studio PRs by resolving and checking out a PR, statically inspecting its changes, running interactive UI tests against a safely tracked Electron instance through CDP, producing a structured report, cleaning up only the owned test instance, and restoring the original branch.
npx skills add CherryHQ/cherry-studio --skill cherry-pr-test --agent claude-code
Same command for any agent — swap --agent for codex, cursor, copilot.
Weekly change comes from our own snapshots, not the repository page — it measures attention, not adoption.
# Cherry Studio PR Test Use this workflow for a bounded PR test. Use `cherry-electron-dev` for ongoing implementation or debugging in the current checkout. ## Prerequisites and safety - Require authenticated `gh`, `pnpm`, and installed project dependencies. - Use Playwright/CDP or optional `agent-browser` for UI control. - Before touching Electron, read [Electron Instance Management](../cherry-electron-dev/references/electron-instance.md) and select its `ephemeral` policy. - Treat that reference as the only authority for discovery, target selection, launch, replacement, shutdown, tracking, and troubleshooting. - Never discard local changes. Stop and ask if checkout would overwrite them. - Show the report before posting it anywhere. `$ARGUMENTS` may contain a PR number, PR URL, `latest`/`recent`, or nothing. ## Workflow ### 1. Resolve and inspect the PR If no PR is specified, list recent PRs and ask the user to choose unless they requested the latest: ```bash gh pr list --repo CherryHQ/cherry-studio --state open --limit 10 \ --json number,title,author,createdAt,headRefName,changedFiles ``` Record the current branch for restoration, inspect the PR, then check it out: ```bash git stat
- Prerequisites and safety
- Workflow
- 1. Resolve and inspect the PR
- 2. Analyze and start the app
- 3. Run interactive tests
- 4. Clean up and restore
- 5. Report
gh pr list --repo CherryHQ/cherry-studio --state open --limit 10 \ git status --short git branch --show-current gh pr view <NUMBER> --json title,body,author,headRefName,files gh pr checkout <NUMBER> pnpm typecheck mkdir -p /tmp/pr-<NUMBER> git checkout <ORIGINAL_BRANCH>
What does the cherry-pr-test skill do?
Test Cherry Studio PRs by resolving and checking out a PR, statically inspecting its changes, running interactive UI tests against a safely tracked Electron instance through CDP, producing a structured report, cleaning up only the owned test instance, and restoring the original branch.
How do I install it?
Run `npx skills add CherryHQ/cherry-studio --skill cherry-pr-test --agent claude-code` — it drops the skill into your project so the agent can pick it up. Swap the --agent value for codex, cursor or copilot if you use one of those.
Where does this skill come from?
From CherryHQ/cherry-studio, a repository with 49,400 stars. We read it straight from the repository tree rather than a submitted listing, so what you see here is what is actually published.
Is a popular skill a good skill?
Not necessarily. Stars measure attention, not adoption — a repository can trend for a week and be abandoned. That is why we show the weekly change from our own snapshots next to the total, instead of a single flattering number.