cy-review-round

Generate structured review issue files for PRD implementations using git diff scope.

1|Updated May 3, 2026
One-click install
npx skills add https://github.com/MatheusBBarni/symphony-orchestrator --skill cy-review-round-matheusbbarni
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: cy-review-round
Source: https://github.com/MatheusBBarni/symphony-orchestrator/tree/main/.agents/skills/cy-review-round
Command: npx skills add https://github.com/MatheusBBarni/symphony-orchestrator --skill cy-review-round-matheusbbarni

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Performs a structured code review of a PRD implementation and produces a review round directory with issue files compatible with cy-fix-reviews. This enables teams to run a manual or standalone quality audit when external providers are not available.

Core Features & Use Cases

  • Generates a dedicated review round directory (reviews-NNN) under .compozy/tasks/<name>/ for a given feature.
  • Reads PRD context from _prd.md, _techspec.md, and _tasks.md, and ADRs from .compozy/tasks/<name>/adrs/ to align the review with architectural decisions.
  • Creates issue files using the canonical issue template, ensuring frontmatter contains required fields and round metadata for downstream tooling.

Quick Start

Run the cy-review-round skill to perform a structured code review on the current branch and generate a new review round directory for cy-fix-reviews.

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 a structured code review for a PRD implementation?

Automate structured code review by running the skill to identify quality issues in PRD implementations and generate structured issue files for the cy-fix-reviews workflow. It cross-checks implementation against review criteria and records round metadata in each issue file.

What is the best way to scope a code quality audit to only changed files?

Scope a code quality audit to changed files by using git diff main...HEAD. If no explicit scope is provided, the skill automatically determines changes on the current branch and limits the review to those touched files within the PRD directory.

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

Generate compatible review issue files by creating them using the canonical issue template with required frontmatter fields and round metadata. The skill formats findings into these files within a dedicated review round directory for downstream automation.

Does the code review process read architectural decision records?

Yes, the code review process reads ADRs from the .compozy/tasks/<name>/adrs/ directory to align the review with architectural decisions. It also reads PRD context from _prd.md, _techspec.md, and _tasks.md files.

Can I run a manual quality audit when external review providers are unavailable?

Yes, you can run a manual or standalone quality audit when external providers are not available. The skill performs a structured code review of a PRD implementation and produces a review round directory with issue files for manual tracking.