| name | ry-review |
| description | Ревью ry-review: сделай ревью, report-only diff/PR/scope, find problems. Используй для: найди проблемы. EN: code review. |
ry-review
Purpose
Find real issues before merge or deploy. Default mode is report-only: do not edit files unless the user explicitly asks after seeing findings.
Workflow
- Determine review target: current diff, branch vs main, PR, file scope, or prompt scope.
- Initialize missing context with
ry-init if needed.
- Use Serena to map changed symbols and affected integration graph.
- Use
rldyour-explore for current implementation best practices when the review depends on external technology behavior.
- Run reviewer tracks. Use subagents when this review request or an explicit-review
ry-start request calls for parallel review.
- Consolidate findings by severity and confidence. Validate uncertain findings with code evidence.
- Output Russian report with exact paths, impact, suggested fixes, and whether each finding is must-fix.
Review Target Parsing
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.
Reviewer Tracks
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
