cy-review-round

To generate a manual code review round for a PRD implementation, provide the feature name so the skill can locate the PRD, techspec, and tasks. It then computes the next review directory and writes deduplicated issue files with correct YAML frontmatter.

Issue deduplication in code review tracking prevents re-flagging issues already present in earlier review rounds. The skill detects the next reviews directory, compares new findings against existing ones, and writes only new, deduplicated issues.

Yes, you can scope a manual PRD code review by providing specific paths. The skill uses the feature name to discover the full scope but optionally accepts user-provided paths to limit the review and issue generation.

Quality audit categories checked during a review round include security, correctness, concurrency, performance, error handling, maintainability, testing, architecture, and operations. The skill flags issues across these dimensions and skips empty rounds.

No, you do not need an external review provider to create issue files. The skill produces a structured manual review round and generates issue files compatible with cy-fix-reviews entirely on its own.

You should skip creating a review round directory when the audit yields no new issues. The skill automatically skips empty rounds and avoids writing files if deduplicated issues are not found.