cy-fix-reviews

Remediate batched PR review issues by updating markdown files and verifying fixes.

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

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Provider-agnostic PR review remediation using prebuilt review round files located under .compozy/tasks/<name>/reviews-NNN/. It helps teams resolve batched review issues quickly by standardizing triage, updates, and fixes without depending on a specific provider.

Core Features & Use Cases

  • Uses existing review round files to scope and drive remediation.
  • Updates issue markdown frontmatter status from pending to valid or invalid, with concrete triage notes.
  • Implements fixes in the scoped files and runs verification to ensure correctness.

Quick Start

Run the remediation workflow on the current batch using existing review round files.

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 for batched code issues?

Automate batched PR review remediation by applying prebuilt round files to triage issues, update markdown frontmatter status, implement fixes, and run verification. This standardizes the remediation workflow across batches without depending on specific providers.

What is a provider-agnostic PR review workflow?

A provider-agnostic PR review workflow uses existing review round files to scope and drive remediation, resolving batched code review issues independently of the hosting platform. It standardizes triage and updates issue markdown status.

How do I update issue markdown frontmatter status during code review triage?

Update issue markdown frontmatter status by triaging batched review issues from pending to valid or invalid. This workflow applies concrete triage notes directly to the issue markdown files located in the configured review round directories.

Does this code review remediation process require a specific Git hosting provider?

No, this code review remediation process is completely provider-agnostic. It drives remediation using existing prebuilt review round files and batched issue metadata, ensuring changes are correct and auditable without depending on specific platforms.

How do I verify fixes after remediating batched PR review issues?

Verify fixes after remediating batched PR review issues by running verification steps configured within the PRD review workflow. This ensures implemented changes in scoped files are correct and auditable before finalizing the batch.

What is the best way to standardize triage for batched code review issues?

The best way to standardize triage for batched code review issues is applying prebuilt review round files to drive remediation. This approach updates issue markdown frontmatter from pending to valid or invalid with concrete triage notes.