cy-review-round

Review PRD implementation code and generate structured issue files.

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

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

It provides a structured way to manually review PRD implementation code and generate a review round directory containing issue files that can be processed by the cy-fix-reviews workflow.

Core Features & Use Cases

  • Determines the next review round number and creates the appropriate directory only when new issues are found.
  • Scopes the review based on PRD specifications, ADRs, and optional user‑provided paths, prioritizing critical files.
  • Evaluates code against nine detailed criteria, deduplicates similar problems, and produces well‑formatted issue markdown files with metadata.
  • Generates round metadata, a concise summary, and guidance for subsequent automated fixing.

Quick Start

Request a review round for the feature named “my-feature” to create a new review 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 manually review PRD implementation code and generate issues?

Manually reviewing PRD implementation code involves evaluating changes against PRD specifications and ADRs. This Skill scopes critical files, deduplicates similar problems, and generates structured markdown issue files formatted for automated fixing workflows.

What criteria are used for a manual PRD code review?

A manual PRD code review evaluates code against nine detailed criteria to ensure quality. It scopes the review based on PRD specifications, ADRs, and optional user-provided paths to prioritize critical files and deduplicate similar problems.

How do I create a structured review round directory for code changes?

Creating a structured review round directory requires determining the next review round number. This Skill automatically creates the appropriate directory and generates issue files only when new code review problems are found.

Can I generate issue files for automated fixing without external providers?

Yes, you can generate issue files for automated fixing without external providers. This Skill conducts a manual quality audit of code changes and produces well-formatted markdown issue files following the cy-fix-reviews format.

What do I need to perform a quality audit of PRD code changes?

To perform a quality audit of PRD code changes, you need access to the PRD task directory and reference criteria files. The Skill then evaluates the code and produces round metadata, a concise summary, and guidance for subsequent automated fixing.

Why does my PRD code review not generate a new review round directory?

A PRD code review does not generate a new review round directory when no new issues are found. The Skill only creates the appropriate directory and issue files if actual problems are identified during the manual code review.