cy-review-round

Reviews PRD implementations and generates structured issue files for downstream fix workflows.

Updated May 19, 2026
One-click install
npx skills add https://github.com/lucasocosta/reeve --skill cy-review-round-lucasocosta
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: cy-review-round
Source: https://github.com/lucasocosta/reeve/tree/main/skills/cy-review-round
Command: npx skills add https://github.com/lucasocosta/reeve --skill cy-review-round-lucasocosta

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve? Manually auditing a completed PRD implementation against its requirements is slow and inconsistent, and review findings often lack a structured format that automated fix workflows can consume. This Skill performs a disciplined code review and writes standardized issue files that the cy-fix-reviews workflow can process directly. ## Core Features & Use Cases - Requirements cross-checking: Validates the implementation against _prd.md, _techspec.md, _tasks.md, and ADRs, flagging missing or deviating requirements as correctness issues. - Severity-ranked issue files: Generates issue_NNN.md files with YAML frontmatter (severity, file, line, round, status) inside a reviews-NNN directory, deduplicated and filtered against linter findings. - Workflow handoff: Emits a structured emit_handoff payload with issue summaries and target files so the fix step can act immediately. - Use Case: After finishing a feature branch, run the review to produce .compozy/tasks/<name>/reviews-001/ with precise, non-duplicated issues, then run compozy reviews fix to remediate them. ## Quick Start Review the implementation of the feature named 'user-auth' and create a review round with issue files for any problems found.

Frequently Asked Questions about cy-review-round

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I review a PRD implementation before merging?▼

Provide the feature name identifying the .compozy/tasks/<name>/ directory. The review reads the PRD, tech spec, tasks, and ADRs, diffs the branch against main, evaluates nine areas including security and correctness, and writes issue files into a reviews-NNN directory.

How are code review issues structured for automated fixing?▼

Each issue becomes an issue_NNN.md file with YAML frontmatter containing provider, round, status, file, line, severity, and author fields, plus a review comment and triage section. This format is parsed by the cy-fix-reviews workflow for remediation.

Does the review avoid duplicate issues across rounds?▼

Yes. Before writing, it reads all prior reviews-NNN directories and only reports new issues not already tracked. It also deduplicates repeated patterns into one representative issue listing all affected files.

Can the review run without a PRD or tech spec?▼

Yes, but it warns that requirements context is missing and proceeds with a code-quality-only review. If neither document exists, findings are limited to the nine evaluation areas rather than requirement compliance.

What happens when the code review finds no issues?▼

The review reports the implementation as clean and does not create a review round directory or any issue files. It emits a handoff with status completed instead of needs_revision.

Does this skill fix the issues it finds?▼

No. It is review-only and never modifies source code. Remediation is handled separately by the cy-fix-reviews workflow, which consumes the generated issue files.