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`.

Quality

85%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

Securityby

Low

Low-risk findings worth noting

Quality

Content

78%Weight 40%Scale 1-5

Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.

A well-structured router that is concise, actionable, and uses clean one-level-deep progressive disclosure to five real reference files. The main improvement room is moving a few validation/feedback checkpoints inline rather than delegating them entirely to the referenced files.

Suggestions

Move one or two explicit validation/feedback checkpoints (e.g., 'after fixes, re-run diff and re-validate') into the body rather than delegating all of them to references, to strengthen workflow_clarity.

Trim the priority-rule block since the route table already encodes the same condition ordering — reference it instead of restating.

Add brief one-line descriptions of what each referenced file covers next to its `→` target, so a reader can navigate without opening every file.

Dimension	Reasoning	Score
Conciseness	A lean router with no padding or concept explanation Claude already knows; the priority-rule block slightly restates route conditions already in the table, the minor over-explanation keeping it just below 5.	4 / 5
Actionability	Concrete executable pre-check commands ("git branch --show-current", "git status --porcelain"), a numbered condition→file route table, an exact question with four labeled options, and a hand-off table mapping options to FIX_MODE values — mostly executable with minor gaps in delegated fix detail.	4 / 5
Workflow Clarity	Clear top-to-bottom sequence with explicit pre-checks and "first applicable rule" ordering; risk-tiered auto-fix modes are defined, but actual validation/feedback checkpoints live in the referenced files rather than inline, a minor gap below 5.	4 / 5
Progressive Disclosure	Body is a clean overview that delegates detail to five well-signaled one-level-deep references (cherry-review-guidance, diagnosis, local-review, pr-review, teams-review), all verified to exist with no nested bundle chains — matches the 5 anchor.	5 / 5
	Total	17 / 20 Passed

Description

92%Weight 40%Scale 1-5

Based on the skill's description, can an agent find and select it at the right time? Clear, specific descriptions lead to better discovery.

A specific, well-triggered description that clearly states both what the skill does and when to use it, with concrete project-specific anchors that distinguish it from generic review skills. Slightly more trigger-term synonym coverage could push it higher.

Dimension	Reasoning	Score
Specificity	Lists multiple concrete targets and actions ("local branches, PRs, commits, files, architecture docs, and repository skills") plus specific review domains ("IpcApi and DataApi boundaries", "renderer hooks", "React/UI conventions", "tests") and two review modes — comprehensive coverage, not a 4.	5 / 5
Completeness	Explicitly answers both — "Automated Cherry Studio review for..." (what) and "Use for code or documentation reviews that need..." (when) with concrete trigger phrases, matching the 5 anchor.	5 / 5
Trigger Term Quality	Strong natural terms a user would say ("code review", "documentation reviews", "PRs", "commits", "architecture docs", "/gh-pr-review diag"); good coverage but a few common synonyms/specific phrasings are missing, so below 5.	4 / 5
Distinctiveness Conflict Risk	Cherry-Studio-specific triggers ("IpcApi and DataApi boundaries", "main/renderer/shared placement", "renderer hooks") carve a clear niche with minimal overlap with generic review skills.	5 / 5
	Total	19 / 20 Passed

Validation

100%

Warnings & errors only

Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.

Validation — 16 / 16 Passed

Validation for skill structure

No warnings or errors.

Repository: CherryHQ/cherry-studio
Path: .agents/skills/gh-pr-review/SKILL.md
Commit: c649419

Reviewed: 3 days ago

Table of Contents

Discovery Implementation Validation

Is this your skill?

If you maintain this skill, you can claim it as your own. Once claimed, you can manage eval scenarios, bundle related skills, attach documentation or rules, and ensure cross-agent compatibility.