cy-review-round

Generate a review round with issue files for PRD-implemented code.

2.5k|134|Updated Mar 28, 2026
One-click install
npx skills add https://github.com/compozy/compozy --skill cy-review-round-compozy
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: cy-review-round
Source: https://github.com/compozy/compozy/tree/main/.agents/skills/cy-review-round
Command: npx skills add https://github.com/compozy/compozy --skill cy-review-round-compozy

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

Quickly and reproducibly review PRD-implemented code by producing a structured review round directory with issue files compatible with cy-fix-reviews. This enables quality-assured handoff and auditability without relying on external providers or manual, ad-hoc reviews.

Core Features & Use Cases

  • Generates a dedicated review round directory derived from the feature path ( .compozy/tasks/<name>/ ) and a standardized reviews-NNN naming scheme.
  • Creates issue files for new findings in the cy-fix-reviews format to guide remediation and tracking.
  • Produces a round metadata file that summarizes total issues, status, and provenance for manual follow-up.

Quick Start

Provide the feature name identifying the target PRD task directory and optionally scope specific files to review, then initiate the review to produce the round directory.

Frequently Asked Questions about cy-review-round

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

FAQPage Schema
How do I automate code reviews for PRD-implemented features?

Automate PRD code reviews by generating a structured review round directory with issue files containing file references, severities, and a manual round meta file to guide remediation and tracking.

What is a structured PRD code review round and when do I need it?

A PRD code review round is a scoped directory of issue files mapped to architecture decisions and related tasks, needed when you require reproducible, auditable quality-assurance handoffs without ad-hoc manual reviews.

How do I generate review issue files compatible with cy-fix-reviews?

Generate cy-fix-reviews compatible issue files by initiating a review against a feature task directory, which automatically produces portable, human-readable findings with severities and file references.

Can I scope automated code reviews to specific files within a PRD feature path?

Yes, you can scope reviews to specific files by optionally providing target file parameters alongside the feature name identifying the target PRD task directory before initiating the review process.

Does this code review automation work without external providers or dependencies?

Yes, this code review automation operates entirely without external providers or dependencies, producing a standardized reviews-NNN naming scheme and a round metadata file for manual follow-up.

What limitations exist when scoping architecture decisions and related tasks for review?

Reviews are scoped strictly to PRD-related files, architecture decisions, and related tasks within the feature path, meaning unrelated code changes outside the target PRD task directory are excluded from the issue map.