Install any skill in seconds. Free to start, no credit card required.
Get Started Free →cherryhq/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.
Passed 15 of 18 test cases with the skill, and 5 of 18 without it.
and 10 more in the full report
13 fixed5 passed either way3 still failing1 broke
Tokens, turns and time describe resource use, not a dollar price.
One of 12 test cases the skill fixed. Same model, same prompt, with and without the skill.
The user invoked the PR test tool with no arguments specified. What command should be run to inspect candidate PRs?
| Checked | Without skill | With skill |
|---|---|---|
| The CLI command lists open PRs for repository CherryHQ/cherry-studio | Missed | Passed |
The instructions your model reads when the skill loads.
Use this workflow for a bounded PR test. Use cherry-electron-dev for ongoing
implementation or debugging in the current checkout.
gh, pnpm, and installed project dependencies.agent-browser for UI control.ephemeral policy.$ARGUMENTS may contain a PR number, PR URL, latest/recent, or nothing.
If no PR is specified, list recent PRs and ask the user to choose unless they requested the latest:
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:
git status --short
git branch --show-current
gh pr view <NUMBER> --json title,body,author,headRefName,files
gh pr checkout <NUMBER>
test cases passed, vs 5 / 18 without
More skills from the same source and nearby in the registry, with their headline benchmark lift.