cy-fix-reviews

Remediate batched PR review issues using pre-existing review round files.

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

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Remediates provider-agnostic PR reviews by reusing pre-existing review round files located under .compozy/tasks/cy-fix-reviews/reviews-NNN/. This streamlines handling batched review issues, updates issue markdown files, applies fixes, and verifies results according to the round's workflow.

Core Features & Use Cases

  • Reuses predefined review round files to scope and execute fixes for multiple issues in a batch.
  • Automates triage, updates issue frontmatter from pending to valid/invalid, and records the rationale for each conclusion.
  • Validates changes through the provider-specific verification workflow, ensuring compliance and traceability.

Quick Start

Execute the remediation workflow for the specified batch of review issues using the designated review round directory.

Frequently Asked Questions about cy-fix-reviews

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I automate PR review remediation across multiple repositories?

Automating PR review remediation across multiple repositories involves reusing predefined review round files to scope and execute batch fixes. The process updates issue markdown frontmatter, applies code fixes, and validates results according to the round's workflow.

What is the process for triaging batched pull request review issues?

Triage for batched pull request review issues involves reading round metadata and batch scope files to evaluate issues. You update issue markdown frontmatter from pending to valid or invalid, recording the rationale for each conclusion.

How do I update markdown frontmatter for batched review issues?

Updating markdown frontmatter for batched review issues requires reading the round metadata file and batch scope. You then change the issue status from pending to valid or invalid and document the rationale directly within the markdown file.

Do I need pre-existing review round files to remediate batched PR issues?

Yes, you need pre-existing review round files located under the tasks directory. These files provide the necessary round metadata and batch scope required to operate and scope fixes for multiple issues.

How do I verify code fixes after remediating pull request reviews?

Verifying code fixes after remediating pull request reviews uses a final verification workflow to confirm correctness. This ensures all applied changes comply with the round's workflow and maintain traceability before completion.

When should I use a batch processing approach for PR review remediation?

Use batch processing for PR review remediation when handling multiple review issues across different repositories. This approach streamlines handling by reusing round files to scope and execute fixes for all issues in the batch.