cy-review-round

Generate a review-round directory with structured issue files from PRD context.

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

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill helps teams systematically audit and document code-review outcomes by generating a structured review-round directory with per-issue files that can be consumed by the cy-fix-reviews workflow.

Core Features & Use Cases

  • Generates a dedicated review round directory (reviews-NNN) with issue files per problem discovered.
  • Reads PRD context and ADRs to align the review against defined requirements, and preserves a change history for traceability.
  • Produces a meta file for manual review rounds and keeps issues organized for downstream remediation.

Quick Start

Start a review round by invoking cy-review-round on the target PRD task to produce a new review round directory 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 automate code-review rounds and document issues systematically?

To automate code-review rounds, you can generate a structured review-round directory containing individual issue files. This ensures code changes are systematically audited and documented for downstream remediation.

What is a manual review round in a CI/CD pipeline?

A manual review round is a quality audit of code changes performed without external providers. It generates a review-round directory with structured issue files and a meta file to track manual code-review outcomes.

How do I document bug tracking issues against PRD requirements?

You document bug tracking issues by reading PRD context and ADRs to align the review against defined requirements. It then produces structured issue files with frontmatter to ensure traceability of discovered problems.

Can I perform a quality audit of code changes without external CI/CD providers?

Yes, you can perform a quality audit without external CI/CD providers by creating a manual review round. This approach reads existing PRD context and ADRs to generate structured issue files locally.

How do I start a code-review round for implemented PRD tasks?

Start a code-review round by invoking the review process on your target PRD task. This automatically produces a new review-round directory containing issue files and a meta file for organizing the audit.