cy-fix-reviews

Automate pull request review remediation by processing existing review round files and updating issue markdowns. The workflow reads batch context from _meta.md and batch_scope to identify the provider, round, and code files, enabling consistent and auditable fixes across multiple providers.

The best way to batch fix code review issues is through a strict triage workflow that scopes valid issues based on round metadata. It sequentially remediates issues within the batch scope, updating issue markdowns to track progress and converge on a verified fix.

Issue triage for pull request review rounds works by reading metadata from _meta.md and batch_scope files. This identifies the provider, review round, and specific code files, enforcing a strict triage process to filter and sequence valid issues for remediation.

Yes, you need existing review round files to start PR review remediation. You must provide the batch_issue_files and the review round directory so the workflow can read the necessary batch context, identify the provider, and enforce the strict triage and fix workflow.

Remediated PR review issues are verified using the cy-final-verify dependency. After sequentially fixing valid issues within the batch scope, the workflow relies on this verification step and reports the final status once the batch completes.

Use a batched workflow for pull request review fixes when you need consistent, auditable remediation across multiple providers and review formats. It is ideal for processing scoped issues sequentially with proper validation and testing to converge on a verified fix.