skillboardUpdated every 6 hours
skillboardTest 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.
Cherry Studio PR Test Use this workflow for a bounded PR test. Use for ongoing implementation or debugging in the current checkout. Prerequisites and safety Require authenticated , , and installed project dependencies. Use Playwright/CDP or optional for UI control. Before touching Electron, read Electron Instance Management and select its policy. Treat that reference as the only authority for discovery, target selection, launch, replacement, shutdown, tracking, and troubleshooting. Never…
Full body not shown for this license – view the source on GitHub →Copy a source-pinned command for your client. You run it yourself.
Destination: .claude/skills/cherry-pr-test · pinned to the source commit
git clone https://github.com/CherryHQ/cherry-studio.git
cd cherry-studio
git checkout 18c287b020ff95cc2a12fc389ea4748957fbaf49
mkdir -p ".claude/skills/cherry-pr-test"
cp -r ".agents/skills/cherry-pr-test" ".claude/skills/cherry-pr-test"Review the source before running. This copies files into your project; it is not a one-click install and does not verify runtime safety.
Scanner static-checks@0.1.0 · commit 18c287b020ff. Static checks cannot prove runtime safety – review the source and the exact diff before installing. How checks work.
References parent-directory traversal, which can escape a target directory.
Evidence: ../· fingerprint fa08499e14d0113b