ederfmatos/claude-voice-bridge / .claude/skills/cy-review-round
cy-review-round
VerifiedPerforms a comprehensive code review of a PRD implementation and generates a review round directory with issue files compatible with cy-fix-reviews. Use when reviewing implemented PRD tasks, creating a manual review round without an external provider, or performing a quality audit of code changes. Do not use for fetching reviews from external providers, fixing existing review issues, executing PRD tasks, or editing source code.
| File | Kind | Size |
|---|---|---|
| SKILL.md | skill md | 9.2 KB |
| references/issue-template.md | markdown | 1.9 KB |
| references/review-criteria.md | markdown | 4.4 KB |
references/issue-template.md
View on GitHub# Issue File Template
Use this exact structure for every issue file. The file is parsed by
`reviews.ReadReviewEntries()` and `prompt.ParseReviewContext()`.
## Format
```
---
status: pending
file: path/to/file.go
line: 42
severity: critical|high|medium|low
author: claude-code
provider_ref:
---
# Issue NNN: <concise title summarizing the problem>
## Review Comment
<detailed description of the issue, why it is a problem,
and a suggested fix with a concise code snippet if helpful>
## Triage
- Decision: `UNREVIEWED`
- Notes:
```
## Field Definitions
- **NNN**: Three-digit zero-padded issue number (001, 002, ...).
- **status**: Starts as `pending`, then moves through `valid` or `invalid`, and ends as `resolved`.
- **title**: One-line summary of the problem. Maximum 72 characters.
- **file**: Relative path from repository root to the affected source file.
Use `unknown` only when the issue is purely architectural and not tied to a
specific file.
- **line**: Line number where the issue is most visible. Use `0` when no
specific line applies.
- **severity**: Exactly one of `critical`, `high`, `medium`, `low`.
Read `review-criteria.md` for definitions.
- **author**: Always `claude-code` for manual review rounds.
- **provider_ref**: Always empty for manual review rounds.
## Parser Compatibility
- The YAML frontmatter must be valid and parseable by `prompt.ParseReviewContext()`.
- Issue file names must match the pattern `issue_NNN.md` where NNN is a
zero-padded number, for `prompt.ExtractIssueNumber()` to recognize them.
## Rules
- One issue per file. Do not combine multiple unrelated problems.
- The Review Comment must be actionable: state the problem clearly and
provide a concrete suggestion for how to fix it.
- Keep code snippets in Review Comment under 15 lines.
- Keep the title descriptive but short.
Good: "Missing nil check before map access in resolveConfig".
Bad: "Code issue".
Related skills
| Skill | Stars | Updated | Works with | Status | Install |
|---|---|---|---|---|---|
| rea-analysis-optimizationmorluto/reaOptimize REA providers and shared analysis workflows for agent context, latency, CPU, and memory while preserving correctness and Evidence. Use for analysis bottlenecks and cache or query design; CI/test-suite optimization belongs to rea-ci-tests-audit. | Stars: 472k | Updated | Claude CodeCodex | Verified | Install |
| rea-ci-tests-auditmorluto/reaAudit REA CI and test suites for correctness, fixture drift, false passes, and measured performance; use for suite or workflow investigations and efficiency changes, rather than ordinary feature testing or a single test failure. | Stars: 472k | Updated | Claude CodeCodex | Verified | Install |
| rea-tool-designmorluto/reaAudit, investigate, design, or change REA investigation tools, CLI/MCP contracts, provider capabilities, and Evidence semantics. | Stars: 472k | Updated | Claude CodeCodex | Verified | Install |
| ponytail-auditDietrichGebert/ponytailQuality audit of the whole repo: bugs, security, real load, missing tests, speed, and what to delete. Most important first. | Stars: 194k | Updated | Claude CodeCodex | Verified | Install |