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

by CherryHQ 52k GitHub stars AGPL-3.0-only Updated Sep 21, 2026
↑ GrowingActive Docs Claude CodeCodex
gh-pr-review skill by CherryHQ
Social preview for CherryHQ/cherry-studio

Overview

gh-pr-review is an open-source docs skill for Claude Code and compatible agents, published by CherryHQ. Its author describes it as: “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…”. The project has 52k stars on GitHub and is available under the AGPL-3.0-only license. Add it to your setup with `git clone https://github.com/CherryHQ/cherry-studio ~/.claude/skills/gh-pr-review`.

What gh-pr-review does

Automated code review for local branches, PRs, commits, and files. Detects the review target from arguments, then picks the review engine from diff size and runtime capability. Small diffs use single-agent review (`references/local-review.md`). Large diffs use the multi-agent reviewer–verifier flow (`references/teams-review.md`) only when independent subagents are available; otherwise they fall back to single-agent review with that limitation disclosed. PR targets add worktree setup and GitHub submission (`references/pr-review.md`) around the same engine-selection contract.

Best for

What’s inside

The SKILL.md for gh-pr-review is organised into these sections:

  • Interaction and interruption contract
  • Review Stages
  • Stage 1: Product Demand gate
  • Authority model
  • Validation after applied fixes
  • Route
  • Rules
  • Scope derivation
  • Usage examples

Installation

Add gh-pr-review to your agent with:

git clone https://github.com/CherryHQ/cherry-studio ~/.claude/skills/gh-pr-review

Review a skill’s source before installing it — skills can instruct your agent to run commands. This command comes from the skill’s public repository, which is the source of truth for setup steps. New to skills? Read how to install Claude Code skills.

Supported agents

  • Claude Code — declared in the repository topics
  • Codex — declared in the repository topics

License

gh-pr-review is published under the AGPL-3.0-only license.

Strengths

  • Clear AGPL-3.0-only license — safe to read and adapt within its terms
  • Ships in CherryHQ/cherry-studio, an established project with 52,047 GitHub stars
  • Works with Claude Code, Codex
  • Actively maintained — repository updated in the last 30 days
  • Its repository gained 2,859 GitHub stars over the last 52 days

Author

CherryHQ 37 skills in the catalog · GitHub profile ↗
View skills

Topics

Need a skill like this, tailored to your team?Build a custom skill →

Frequently asked questions

What does gh-pr-review 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. 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`.
How do I install gh-pr-review?
Run git clone https://github.com/CherryHQ/cherry-studio ~/.claude/skills/gh-pr-review in your agent, then reload your skills. Review the source at https://github.com/CherryHQ/cherry-studio before installing.
Is gh-pr-review free to use?
Yes. gh-pr-review is free and open source under the AGPL-3.0-only license, so you can read, run, and adapt it within that license's terms.
Which agents does gh-pr-review work with?
gh-pr-review lists Claude Code and Codex — named in its SKILL.md, its plugin marketplace or its repository topics. Skills use the portable SKILL.md format, so other agents that read that format may load it too.
Where does gh-pr-review come from?
gh-pr-review ships inside CherryHQ/cherry-studio, a repository that contains 37 catalogued skills in total. The repository's 52,047 GitHub stars apply to that whole collection, not to this skill on its own.

Related skills

More Docs skills →

Derive new Office files from structural selections without touching the original. Use when the user points at part of a spreadsheet, Word document, PDF, or PowerPoint deck (a worksheet range, paragraph, page, slide, shape, or a pasted selection-ref block) and wants it extracted, converted, or edited — the result is always a NEW file; the source file is never modified. Covers xlsx range extraction to csv/markdown/xlsx, docx paragraph extraction and text replacement, pdf page extraction, pptx slide/shape/table-cell extraction and editing, and targeted xlsx cell edits.

NewActive Claude CodeCodex
52k GitHub stars AGPL-3.0-only Updated Sep 21, 2026 Free

Knowledge and governance closeout: reconcile project docs, rule files (CLAUDE.md/AGENTS.md), authorized agent memory, and workspace residue with what the code and runtime actually do, so the next session or the next person starts from one current answer. Trigger when the user names "neat-freak", "洁癖", or "/neat" — and also on clear knowledge-closeout intent without the name: syncing or tidying project docs/rules/memory after development ("把文档和记忆整理一下", "收尾时把文档同步掉", "docs 和代码对不上了"), stale or conflicting CLAUDE.md/memory, a clean handoff to a teammate or a fresh session, or auditing whether workspace rules are actually followed. Do not trigger for pure coding/refactoring/debugging tasks, tidying data or prose (JSON, 周报, changelog announcements), or a bare "整理" with no project-knowledge context.

Claude CodeCodex
20k GitHub stars MIT Updated Aug 16, 2026 Free

A documentation page — inline-start nav, scrollable article body, inline-end table of contents. Use when the brief mentions "docs", "documentation", "guide", "API reference", or "tutorial".

↑ GrowingActive Claude Code
97k GitHub stars Apache-2.0 Updated Sep 21, 2026 Free

Records decisions and documentation. Use when you need to document an architecture decision (ADR) or the reasoning behind a design choice, when changing public APIs, shipping features, or when you need to record context that future engineers and agents will need to understand the codebase.

↑ GrowingActive Claude CodeCodexCursor+1
98k GitHub stars MIT Updated Sep 20, 2026 Free

Grounds every implementation decision in official documentation. Use when you want to verify an approach against the official docs before implementing it, or when you want authoritative, source-cited code free from outdated patterns. Use when building with any framework or library where correctness matters.

↑ GrowingActive Claude CodeCodexCursor+1
98k GitHub stars MIT Updated Sep 20, 2026 Free