ワンクリックで
ry-review
Ревью ry-review: сделай ревью, report-only diff/PR/scope, find problems. Используй для: найди проблемы. EN: code review.
Codex または Claude でインストール この Prompt をコピーして Codex、Claude、または他のアシスタントに貼り付けると、Skill ページを確認してインストールできます。
メニュー
Ревью ry-review: сделай ревью, report-only diff/PR/scope, find problems. Используй для: найди проблемы. EN: code review.
Codex または Claude でインストール この Prompt をコピーして Codex、Claude、または他のアシスタントに貼り付けると、Skill ページを確認してインストールできます。
SOC 職業分類に基づく
Отлаживает browser-only failures через Chrome DevTools MCP и Playwright CLI. Используй для: консоль, сеть, runtime, layout, memory, performance, Lighthouse. EN triggers: browser debug, console, network, runtime, performance.
Маршрутизирует browser tasks только через managed Playwright CLI и Chrome DevTools MCP. Используй для: UI, визуально, скриншот, Figma, консоль, сеть, перфоманс. EN triggers: browser routing, UI validation, screenshots, visual QA, console, network.
Валидирует UI и сценарии через Playwright CLI evidence. Используй для: проверь UI, браузер, скриншот, регрессия, адаптив, бизнес-логика, визуально. EN triggers: validate UI, browser check, regression, responsive, screenshot.
Низкоуровневая browser automation через Playwright CLI. Используй для: screenshots, snapshots, headed sessions, traces, responsive, UI proof. EN triggers: Playwright CLI validation, screenshots, snapshots, traces.
Проводит visual QA для Figma, screenshots и reference images. Используй для: pixel-perfect, сравни с Figma, сравни с фото, diff. EN triggers: visual diff, pixel-perfect, compare Figma, reference image.
Маршрутизирует старые Webwright-запросы в управляемые CloakBrowser workflows. Используй для: длинная web-задача, RPA, extraction. EN triggers: compatibility browser task, long-horizon web task.
| name | ry-review |
| description | Ревью ry-review: сделай ревью, report-only diff/PR/scope, find problems. Используй для: найди проблемы. EN: code review. |
Find real issues before merge or deploy. Default mode is report-only: do not edit files unless the user explicitly asks after seeing findings.
ry-init if needed.rldyour-explore for current implementation best practices when the review depends on external technology behavior.ry-start request calls for parallel review.When the owner asks for a time-window or history-based review, resolve the review target before dispatching reviewers:
last N days / за последние N дней: compute the exact commit range with
git log --since.since DATE / с DATE: use the explicit date as the lower bound.PR #N or issue #N: inspect the GitHub PR/issue and verify its relevance
against current code before treating it as a finding.branch vs main: review the merge-base diff plus related commits.since last deploy: identify the last verified deployment marker or ask for
it if the repository has no durable deploy record.Report the resolved commit range, PR/issue IDs, and any unresolved evidence gap.
Read references/reviewer-protocol.md. These tracks are orchestrated by ry-review or ry-start; they are not broad implicit-entry skills.
flow-architecture-reviewflow-quality-reviewflow-consistency-reviewflow-integration-reviewflow-verification-reviewflow-security-review when sensitive or requested