Agent skill · Frontend

gh-pr-review

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, renderer hooks, React/UI conventions, and tests. Supports single-agent review with interactive fix selection or multi-agent reviewer-verifier review with risk-based auto-fix. To diagnose gaps in the skill after a review session, run `/gh-pr-review diag`.

CherryHQgithub.com/CherryHQGitHub ↗
claude-codecodexAGPL-3.0
Install
npx skills add CherryHQ/cherry-studio --skill gh-pr-review --agent claude-code

Same command for any agent — swap --agent for codex, cursor, copilot.

Facts
Files in the skill folder: 11
SKILL.md size: 5 KB
Bundled scripts: none
Path: .agents/skills/gh-pr-review/SKILL.md
Open the folder on GitHub →
Where it comes from
Stars: 49,400
Language: TypeScript
Read our review of the source →

Weekly change comes from our own snapshots, not the repository page — it measures attention, not adoption.

From the SKILL.md

<!-- Based on https://github.com/Tencent/tgfx/tree/main/.codebuddy/skills/cr --> <!-- Adapted for agent runtimes and the Cherry Studio tech stack --> # /gh-pr-review — Code Review Automated code review for local branches, PRs, commits, and files. Detects review mode from arguments and routes to the appropriate review flow — either quick single-agent review with interactive fix selection, or multi-agent deep review with risk-based auto-fix. Cherry Studio-specific review rules live in `references/cherry-review-guidance.md`. Target review flows must load that file for code, mixed, architecture-doc, and project-skill reviews so reviewers can apply DataApi, service-boundary, renderer hook, React, UI, and type-contract checks without relying on memory. That reference also defines which internal docs, internal skills, external skills, and official websites to consult for each changed area; load only the relevant subset. All user-facing text matches the user's language. Use the runtime's interactive dialog tool for questions and option selection when one is available; otherwise ask one concise plain-text question and wait for the reply. Do not invent a tool or syntax the runtime does not e

What's inside
Steps it walks through
  1. Route
  2. Question
  3. Hand off
Ships with 10 files
  • agents/openai.yaml
  • references/checklist-evolution.md
  • references/cherry-review-guidance.md
  • references/code-checklist.md
  • references/diagnosis.md
  • references/doc-checklist.md
  • references/judgment-matrix.md
  • references/local-review.md
  • references/pr-review.md
  • references/teams-review.md
More from cherry-studio
All skills →
About this skill
What does the gh-pr-review skill do?

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, renderer hooks, React/UI conventions, and tests. Supports single-agent review with interactive fix selection or multi-agent reviewer-verifier review with risk-based auto-fix. To diagnose gaps in the skill after a review session, run `/gh-pr-review diag`.

How do I install it?

Run `npx skills add CherryHQ/cherry-studio --skill gh-pr-review --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.

Keep going