cy-fix-reviews

Batch PR review remediation resolves issues in critical-to-low severity order by reading triage and status from existing review round files. This ensures critical problems are addressed first and prevents incomplete remediation across the batch scope.

Provider-agnostic review remediation applies code fixes using existing review round issue files as the source of truth, avoiding provider-specific mutations. It relies on round and issue-file frontmatter context to execute changes without fetching or exporting data from specific review providers.

Batch-scoped remediation constrains code edits strictly to files declared in the batch scope, avoiding unrelated refactors. The process reads the declared file boundaries from the existing review round issue files and limits all modifications to that scope.

Yes, verification-first completion runs the repository's real verification workflow before claiming success or creating commits. If verification fails, the process addresses root causes rather than skipping checks, ensuring only validated code changes are committed.

Yes, provider-agnostic remediation works across platforms by using existing review round issue files as the source of truth rather than fetching from specific providers. It forbids provider-specific mutations and applies fixes based on file frontmatter context.

Incomplete remediation often occurs when fixes aren't applied in severity order or when batch scope boundaries aren't enforced. Using existing review round files as the source of truth with strict severity sequencing ensures all declared issues are addressed systematically.