CherryHQ/cherry-studio / .agents/skills/gh-pr-review
gh-pr-review
UnverifiedAutomated 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. Review depth adapts to diff size and runtime subagent capability (single-agent or multi-agent reviewer-verifier). Report-only by default; code fixes and GitHub submission each require explicit invocation-time authorization (`fix` / `submit`). Normal-review prompts and safe interruption behavior follow the interaction contract below. To diagnose gaps in the skill after a review session, run `/gh-pr-review diag`.
| File | Kind | Size |
|---|---|---|
| SKILL.md | skill md | 15.4 KB |
| agents/openai.yaml | config | 247 B |
| references/checklist-evolution.md | markdown | 4.7 KB |
| references/cherry-review-guidance.md | markdown | 40.0 KB |
| references/code-checklist.md | markdown | 10.3 KB |
| references/consumer-review.md | markdown | 7.4 KB |
| references/diagnosis.md | markdown | 2.6 KB |
| references/doc-checklist.md | markdown | 3.8 KB |
| references/judgment-matrix.md | markdown | 6.8 KB |
| references/local-review.md | markdown | 6.2 KB |
| references/pr-review.md | markdown | 19.7 KB |
| references/teams-review.md | markdown | 19.0 KB |
references/diagnosis.md
View on GitHub# Diagnosis
Analyze the most recent `/gh-pr-review` session in this conversation to find
defects in the skill files themselves — checklist gaps, ambiguous instructions,
missing exclusion rules, etc. The goal is to make the skill more accurate and
reliable, NOT to re-review the project code.
This is an explicit maintenance mode under `SKILL.md` § Interaction and
interruption contract, not a normal review. Interactive runs may request the
declared edit selection below. Automated runs never wait for a selection: report
the actionable edit candidates, apply none, and stop.
Work entirely from the session context. Only read a skill file when you need to
confirm the exact wording of a rule before suggesting a change.
## Prerequisites
If no `/gh-pr-review` session exists in the current conversation, inform the
user and stop.
## Analyze
Scan the **entire** session from start to finish for these signals and report
findings. Do not stop after finding the first issue — exhaustively check every
user message and system notification. Key evidence includes user rollbacks of
auto-fixes, manual corrections or overrides the user had to provide, steps the
AI deviated from, and user interventions to unblock a stalled flow (e.g., the
user asking "why did you stop?" or manually prompting the AI to continue). For
each finding, state which skill file to change and what the change should be.
### False positives
Issues reported or auto-fixed that the user rejected, reverted, or corrected.
For each: what was wrong, and which checklist item, exclusion rule, or
judgment-matrix rule should be added or revised.
### Judgment errors
Issues where the user disagreed with the risk level or worth-fixing decision
(e.g., reverted an auto-fix, or explicitly overrode a skip). For each: what
the session assigned vs what it should have been, and how to revise
judgment-matrix.md.
### Flow deviations
Steps the AI skipped, reordered, or executed incorrectly. For each: which
step in which file was violated, and how to clarify the instruction.
### Other improvements
Anything else observed in the session that points to a concrete skill file
change — e.g., redundant steps, missing guardrails, unclear wording. Only
include if the change is specific and actionable.
## Apply
If any finding has a concrete file edit, an interactive run presents all
actionable edits via multi-select. Each option label is a one-line summary of
the edit. Unchecked edits are discarded. An automated run reports the same
candidates without presenting a selection control.
In an interactive run, apply selected edits. In an automated run, apply none.
Related skills
| Skill | Stars | Updated | Works with | Status | Install |
|---|---|---|---|---|---|
| finishing-a-development-branchobra/superpowersUse when implementation is complete, all tests pass, and you need to decide how to integrate the work | Stars: 322k | Updated | Claude CodeCodex | Verified | Install |
| systematic-debuggingobra/superpowersUse when encountering any bug, test failure, or unexpected behavior, before proposing fixes | Stars: 322k | Updated | Claude CodeCodex | Verified | Install |
| test-driven-developmentobra/superpowersUse when implementing any feature or bugfix, before writing implementation code | Stars: 322k | Updated | Claude CodeCodex | Verified | Install |
| skill-creatoranthropics/skillsCreate new skills, modify and improve existing skills, and measure skill performance. Use when users want to create a skill from scratch, edit, or optimize an existing skill, run evals to test a skill, benchmark skill performance with variance analysis, or optimize a skill's description for better triggering accuracy. | Stars: 198k | Updated | Claude CodeCodex | Verified | Install |