gsd-code-review-fix

Automated code review fix workflows target a phase-specific REVIEW.md file to apply scoped fixes. The process validates the phase, checks review status, applies fixes selectively, and generates a REVIEW-FIX.md summary for traceable output.

To commit code review fixes atomically, the workflow processes findings from REVIEW.md and commits each fix individually, ensuring cleaner version history and easier auditing while generating a REVIEW-FIX.md summary to track remediation actions.

The best way to resolve critical and warning findings is using selective fix scope, which targets these high-priority items by default, with an option to include informational items and iterate re-review cycles up to three times to reduce residual issues.

Yes, you can run iterative re-review cycles up to three times to reduce residual code issues. Using the --auto option triggers automated iteration, allowing the workflow to re-run review and fix cycles to improve convergence and resolve feedback completely.

Yes, the review remediation workflow requires a phase-specific REVIEW.md file as input to identify issues, and generates a REVIEW-FIX.md summary file as output to document the applied fixes and maintain traceable audit history.

Selective scope control in bug fixing focuses on critical and warning findings by default, meaning informational items are excluded unless explicitly included with the --all option, preventing scope creep but potentially leaving minor info-level issues unresolved.