cy-review-round

Reviews PRD implementations and generates structured issue files for remediation workflows.

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

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve? Manual code reviews of PRD implementations are inconsistent and produce unstructured feedback that is hard to track and fix. This Skill performs a systematic review against requirements and produces machine-parseable issue files that downstream fix workflows can process automatically. ## Core Features & Use Cases - Structured Review Rounds: Creates numbered reviews-NNN/ directories containing issue_NNN.md files with severity, file, line, and triage frontmatter compatible with the cy-fix-reviews workflow. - Requirements Cross-Checking: Validates the implementation against _prd.md, _techspec.md, and ADRs, flagging missing or deviating requirements as correctness issues. - Severity-Based Triage: Classifies findings as critical, high, medium, or low across nine evaluation areas including security, concurrency, and error handling, with deduplication and lint-overlap filtering. - Use Case: After implementing a feature branch, run a review round to get a merge recommendation, a prioritized issue list, and a _meta.md summary ready for automated remediation. ## Quick Start Review the implementation of the feature named 'user-auth' and generate a new review round with issue files.

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 skill reads the PRD, tech spec, and ADRs, scopes the changed files via git diff, and produces a reviews-NNN directory with severity-tagged issue files and a merge recommendation.

What code review severity levels should I use?▼

Use critical for security flaws, crashes, and data loss; high for correctness bugs and user-visible performance problems; medium for maintainability and test gaps; low for minor improvements. The review-criteria.md reference defines each level with examples.

Does the review round skill fix the issues it finds?▼

No, it only identifies and documents issues as structured issue files. Remediation is handled separately by the cy-fix-reviews workflow, which consumes the generated review round directory.

What happens when a code review finds no issues?▼

The skill reports the implementation as clean and ready to merge without creating a review round directory. This avoids leaving empty reviews-NNN directories in the PRD folder.

Can I scope a code review to specific files or directories?▼

Yes, you can provide explicit file or directory paths to limit the review scope. Without explicit paths, the skill uses git diff against main to discover changed files, and asks you to specify files if the diff is empty.