Gh Pr Review (Cherry Studio)

Cherry Studio's in-house PR/branch recenzent prosazující DataApi/IpcApi a layer-boundary rules.

od CherryHQ · CherryHQ/cherry-studio

Funguje s nastavením ★ 8.4/10

Gh Pr Review (Cherry Studio) — Cherry Studio's in-house PR/branch recenzent prosazující DataApi/IpcApi a layer-boundary rules.

Co umí

Směruje local-branch, PR, commit a file reviews přes Cherry Studio's own architecture rulebook — DataApi/IpcApi boundaries, main/renderer/shared placement, naming conventions a service-ownership rules — nabízí buď quick single-agent pass s interactive fix selection nebo multi-agent reviewer-verifier pass s risk-based auto-fix. Spouští se na Cherry Studio-scoped review requests nebo the /gh-pr-review command; its deepest guidance depends on architecture docs (docs/references/*.md), které live at the Cherry Studio repo root, not inside the skill folder that gets copied on install.

Testovací report

Předložil jsem mu synthetic Cherry-Studio-style diff (a DataApi ipcMain.handle s business logic baked into the handler, plus a renderer component calling window.require('fs') directly): a generic baseline review caught the Electron nodeIntegration smell but missed the DataApi-handler boundary violation entirely, while the skill's guidance flagged both as named Blockers s the exact upstream doc and fix pattern (owning-service method + typed ipcApi.request route) — but that guidance only works because the full monorepo's docs/references/ tree is sitting next to it, which the standard install copy leaves behind.

Testováno: 2026-07-14 · Claude Code 2.x (agent harness)

Instalace

git clone https://github.com/CherryHQ/cherry-studio
cd cherry-studio
mkdir -p ~/.claude/skills
cp -r .agents/skills/gh-pr-review ~/.claude/skills/gh-pr-review

Příkazy a ukázkové prompty

  • /gh-pr-reviewCherry Studio's in-house PR/branch recenzent prosazující DataApi/IpcApi a layer-boundary rules.

Skilly se spouštějí běžnými požadavky — žádné příkazy k zapamatování. Po instalaci ho aktivují prompty jako tyto (anglicky):

  • Review this pull request diff for blockers and fixes
  • Check this PR for IPC bypass and business-logic leaks
  • Do a code review of my changes before I merge