Source profileQuality 71/100

CherryHQ/cherry-studio/.agents/skills/gh-pr-review/SKILL.md

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 s

Source repository stars
49,062
Declared platforms
0
Static risk flags
1
Last source update
2026-07-28
Source checked
2026-07-28
DecisionCompatibilityInstallWorkflowPermissionsEvidenceSource

Decision brief

What it does—and where it fits

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.

Best for

    Not for

    • Tasks that require unconfirmed production actions or broad system permissions.
    • Environments where the pinned source and install steps cannot be inspected.

    Compatibility matrix

    Platform support, with evidence labels

    PlatformStatusEvidenceWhat to check
    CodexNot declaredNo explicit evidencePortability before use
    Claude CodeNot declaredNo explicit evidencePortability before use
    CursorNot declaredNo explicit evidencePortability before use
    Gemini CLINot declaredNo explicit evidencePortability before use
    Open the compatibility checker

    Installation

    Inspect first. Install second.

    The source command is displayed only when detected. A safe inspection prompt is always available so your agent can explain every action before execution.

    Source-detected install commandSource
    npx skills add https://github.com/CherryHQ/cherry-studio --skill ".agents/skills/gh-pr-review"
    Safe inspection promptEditorial

    Inspect the Agent Skill "gh-pr-review" from https://github.com/CherryHQ/cherry-studio/blob/dda7cc99d730c36bde685bec586dafe458722a4d/.agents/skills/gh-pr-review/SKILL.md at commit dda7cc99d730c36bde685bec586dafe458722a4d. List every install step, command, network request, credential, file read/write, external action, and rollback step. Explain whether it fits my task. Do not install or execute anything until I approve.

    Workflow

    What the source asks the agent to do

    1. 01

      Route

      Run pre-checks, then match the first applicable rule top-to-bottom:

      git branch --show-current → record whether on main/master.git status --porcelain → record whether uncommitted changes exist.Check whether the current environment supports parallel subagents (agent
    2. 02

      Question

      Ask a single question: "Agent Teams is available (multiple agents working in parallel). Enable multi-agent review with reviewer–verifier adversarial mechanism and auto-fix?" Provide 4 options:

      Ask a single question: "Agent Teams is available (multiple agents working in parallel). Enable multi-agent review with reviewer–verifier adversarial mechanism and auto-fix?" Provide 4 options:Pass $ARGUMENTS to the target file. For teams-review, also pass FIXMODE (low / lowmedium / full).
    3. 03

      Hand off

      Pass $ARGUMENTS to the target file. For teams-review, also pass FIXMODE (low / lowmedium / full).

      Pass $ARGUMENTS to the target file. For teams-review, also pass FIXMODE (low / lowmedium / full).

    Permission review

    Static risk signals and limitations

    Reads files

    low · line 12

    The documentation asks the agent to read local files, directories, or repositories.

    `references/cherry-review-guidance.md`. Target review flows must load that file

    Reads files

    low · line 44

    The documentation asks the agent to read local files, directories, or repositories.

    Each `→` means: `Read` the target file and follow it as the sole remaining

    Evidence record

    Why each signal appears

    EvidenceSourceComputedTestedEditorial
    SignalValueEvidence typeMeaning
    Quality score71/100ComputedDocumentation, specificity, maintenance, and trust rules
    Repository stars49,062SourceRepository attention, not individual Skill quality
    Compatibility0 platformsSourceDeclared in the catalog source record
    Usage guideautomated source guideEditorialGenerated or reviewed according to the visible evidence level

    Pinned source

    Provenance and original SKILL.md

    Repository
    CherryHQ/cherry-studio
    Skill path
    .agents/skills/gh-pr-review/SKILL.md
    Commit
    dda7cc99d730c36bde685bec586dafe458722a4d
    License
    AGPL-3.0
    Collected
    2026-07-28
    Default branch
    main
    View the original SKILL.md

    /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 expose. For interactive multi-select: ≤4 items → one question. >4 items → group by priority or category (each group ≤4 options), then present all groups in one prompt.

    Route

    Run pre-checks, then match the first applicable rule top-to-bottom:

    1. git branch --show-current → record whether on main/master.
    2. git status --porcelain → record whether uncommitted changes exist.
    3. Check whether the current environment supports parallel subagents (agent teams), using the runtime-provided coordination tools.
    #ConditionAction
    1$ARGUMENTS is diag→ references/diagnosis.md
    2$ARGUMENTS is a PR number or URL containing /pull/→ references/pr-review.md
    3Agent teams NOT supported→ references/local-review.md
    4Uncommitted changes exist→ references/local-review.md
    5On main/master branch→ references/local-review.md
    6Everything else→ Question below

    Each → means: Read the target file and follow it as the sole remaining instruction. Ignore all sections below. Do NOT review from memory or habit — each target file defines specific constraints on how to obtain diffs, apply fixes, and submit results.

    Priority rule: user intent (Rule 1, 2, 6) takes priority over working-tree state (Rule 3, 4, 5). A PR URL or PR number always goes to references/pr-review.md even when the working tree is dirty or the current branch is main/master — those state conditions only apply when the user did not specify a review target.

    Question

    Ask a single question: "Agent Teams is available (multiple agents working in parallel). Enable multi-agent review with reviewer–verifier adversarial mechanism and auto-fix?" Provide 4 options:

    OptionDescription
    Teams + auto-fix low & medium risk (recommended)Multi-agent review; auto-fix most issues, only confirm high-risk ones (e.g., API changes, architecture).
    Teams + auto-fix low riskMulti-agent review; auto-fix only the safest issues (e.g., null checks, typos, naming). Confirm everything else.
    Teams + auto-fix allMulti-agent review; auto-fix everything. Only issues affecting test baselines are deferred.
    Single-agent + manual fixSingle-agent review; interactively choose which issues to fix afterward.

    Hand off

    Option→FIX_MODE
    Teams + auto-fix low & medium risk (recommended)references/teams-review.mdlow_medium
    Teams + auto-fix low riskreferences/teams-review.mdlow
    Teams + auto-fix allreferences/teams-review.mdfull
    Single-agent + manual fixreferences/local-review.md—

    Pass $ARGUMENTS to the target file. For teams-review, also pass FIX_MODE (low / low_medium / full).

    Alternatives

    Compare before choosing

    Computed 89165

    JasonColapietro/suede-creator-skills

    suede-code-review

    Find the bugs a diff can actually ship: TypeScript, React, Next.js, OWASP, accessibility, SEO, database, and deploy-risk review. Return findings, not a grade.

    2026-07-280 platforms
    Computed 81234,327

    affaan-m/ECC

    coding-standards

    Baseline cross-project coding conventions for naming, readability, immutability, and code-quality review. Use detailed frontend or backend skills for framework-specific patterns.

    2026-07-270 platforms
    Computed 79234,327

    affaan-m/ECC

    coding-standards

    Baseline cross-project coding conventions for naming, readability, immutability, and code-quality review. Use detailed frontend or backend skills for framework-specific patterns.

    2026-07-270 platforms
    Computed 75234,327

    affaan-m/ECC

    coding-standards

    Universal coding standards, best practices, and patterns for TypeScript, JavaScript, React, and Node.js development.

    2026-07-270 platforms