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.
gh-pr-review
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 51k 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 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.
Installation
Add gh-pr-review to your agent with:
git clone https://github.com/CherryHQ/cherry-studio ~/.claude/skills/gh-pr-reviewAlways review a skill's source before installing it. This command comes from the skill's public repository; the linked repo is the source of truth for exact setup steps.
What's inside
The SKILL.md for gh-pr-review is organised into these sections:
- Route
- Question
- Hand off
When to use it
Reach for gh-pr-review when you want docs help from your agent without writing the same instructions every session. Load the skill and the agent picks it up automatically for relevant tasks.
Strengths
- Clear AGPL-3.0-only license — safe to read and adapt
- Ships in CherryHQ/cherry-studio, an established project with 50,722 GitHub stars
- Actively maintained (recent commits)
Topics
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. 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 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.
- Where does gh-pr-review come from?
- gh-pr-review ships inside CherryHQ/cherry-studio, a repository that contains 20 catalogued skills in total. The repository's 50,722 GitHub stars apply to that whole collection, not to this skill on its own.
Related skills
More Docs →
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".
Records decisions and documentation. Use when making architectural decisions, changing public APIs, shipping features, or when you need to record context that future engineers and agents will need to understand the codebase.
Grounds every implementation decision in official documentation. Use when you want authoritative, source-cited code free from outdated patterns. Use when building with any framework or library where correctness matters.
Yao process documentation expert. ALWAYS invoke this skill when the user needs to discover available processes, read process signatures, or validate process names. Do not guess process APIs — use this skill first.