cy-fix-reviews

Triage and resolve batched PR review issues from existing review round files.

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

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? After a code review round is exported into issue files, someone still has to read each issue, decide if it is valid, implement the fix, and verify nothing broke. This Skill automates that remediation loop so review feedback is resolved consistently and traceably. ## Core Features & Use Cases - Issue triage: Reads every scoped issue file, marks each as valid or invalid, and records technical reasoning in the file's Triage section. - Severity-ordered fixes: Implements production-quality fixes for valid issues in critical-to-low order, with tests updated when behavior changes. - Verified completion: Runs the repository's real verification workflow before marking issues resolved or committing, and documents pre-existing failures instead of reverting fixes. - Use Case: A reviewer leaves 12 comments on a pull request. The review round files already exist under .compozy/tasks/<name>/reviews-NNN/. This Skill triages all 12, fixes the 9 valid ones, documents why 3 are invalid, runs the test suite, and leaves a clean diff for review. ## Quick Start Resolve the batched review issues in the current review round directory and verify the fixes before committing.

Frequently Asked Questions about cy-fix-reviews

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

FAQPage Schema
How do I fix PR review comments in bulk?▼

Place the exported review round files under .compozy/tasks/<name>/reviews-NNN/ and run this remediation workflow. It reads every scoped issue file, triages each as valid or invalid, fixes valid issues in severity order, and verifies the result before completion.

How to triage code review issues automatically?▼

The workflow reads each issue file completely, then sets its frontmatter status to valid or invalid with concrete technical reasoning recorded in the Triage section. Valid issues get a root cause and fix approach; invalid ones get a documented justification.

Does this workflow fetch reviews from GitHub or GitLab?▼

No. Fetching and exporting reviews is handled separately before this workflow runs. It only consumes review round files that already exist on disk and never calls provider-specific scripts or gh mutations.

What happens if verification fails after fixing review issues?▼

The workflow fixes the failing checks in the changed code rather than reverting fixes. If the failure is pre-existing and unrelated, it is documented in the issue file's Triage section and the run proceeds.

When should I not use this review remediation workflow?▼

Do not use it for PRD task execution, review export or fetching, or general coding tasks without existing review issue files. It requires a scoped batch of issue markdown files to operate.