cherry-pr-test

Featured

Test Cherry Studio PRs by checking out the branch, launching the Electron app in debug mode, and running interactive UI tests via CDP.

Testing & QA 43,225 stars 4056 forks Updated 4 days ago AGPL-3.0

Install

View on GitHub

Quality Score: 90/100

Stars 20%
100
Recency 20%
100
Frontmatter 20%
70
Documentation 15%
100
Issue Health 10%
50
License 10%
100
Description 5%
100

Skill Content

# Cherry Studio PR Test Automated PR testing workflow for Cherry Studio. Checks out a PR, launches the Electron app with Chrome DevTools Protocol, connects agent-browser, and runs interactive UI + code review tests. ## Prerequisites - `gh` CLI installed and authenticated - `agent-browser` installed (for CDP-based UI testing) - `pnpm` installed with project dependencies (`pnpm install`) ## Constraints - Always kill existing Cherry Studio processes before launching a new instance. - Never leave debug processes running after testing completes. - Always switch back to the default branch after testing. - Always show the test report to the user before posting it. ## Arguments `$ARGUMENTS` may contain: - A PR number (e.g., `13955`) - A PR URL (e.g., `https://github.com/CherryHQ/cherry-studio/pull/13955`) - Keywords like "latest", "recent" to pick a recent PR - Empty — list recent PRs and let the user choose ## Workflow ### Phase 1: Select & Checkout PR 1. If no PR number given, list recent open PRs: ```bash gh pr list --repo CherryHQ/cherry-studio --state open --limit 10 \ --json number,title,author,createdAt,headRefName,changedFiles \ --template '{{range .}}#{{.number}} | {{.title}} | by {{.author.login}} | files: {{.changedFiles}} {{end}}' ``` 2. Ask the user to pick one (or auto-pick if "latest"/"recent"). 3. View PR details to understand what changed: ```bash gh pr view <NUMBER> --json title,body,headRefName,files ``` 4. Checkout the PR b...

Details

Author
CherryHQ
Repository
CherryHQ/cherry-studio
Created
1 years ago
Last Updated
4 days ago
Language
TypeScript
License
AGPL-3.0

Integrates with

Similar Skills

Semantically similar based on skill content — not just same category

Code & Development Listed

push-pr

Push current branch and create a GitHub PR if one doesn't exist

20 Updated 5 days ago
sapiencexyz
Testing & QA Featured

browser-testing-with-devtools

Tests in real browsers. Use when building or debugging anything that runs in a browser. Use when you need to inspect the DOM, capture console errors, analyze network requests, profile performance, or verify visual output with real runtime data via Chrome DevTools MCP.

10,628 Updated 4 days ago
addyosmani
Code & Development Featured

pr-create

Creates a pull request from current changes, monitors GitHub CI, and debugs any failures until CI passes. Use this when the user says "create pr", "make a pr", "open pull request", "submit pr", "pr for these changes", or wants to get their current work into a reviewable PR. Assumes the project uses git, is hosted on GitHub, and has GitHub Actions CI with automated checks (lint, build, tests, etc.). Does NOT merge - stops when CI passes and provides the PR link.

259 Updated 2 weeks ago
posit-dev
Code & Development Solid

github-pr-creation

Creates GitHub Pull Requests with automated validation and task tracking. Use when user wants to create PR, open pull request, submit for review, or check if ready for PR. Analyzes commits, validates task completion, generates Conventional Commits title and description, suggests labels. NOTE - for merging existing PRs, use github-pr-merge instead.

56 Updated 3 weeks ago
fvadicamo
Code & Development Solid

claude-code-review

Use when asked to review a PR, or when /review is invoked with a PR number or URL. Performs a focused code review checking for bugs, security, performance, and test gaps, then posts findings as a PR comment and formal GitHub review.

450 Updated 4 days ago
DataRecce