gsd-code-review-fix

Automatically fixing code review issues is handled by spawning a fixer agent that applies changes recorded in REVIEW.md. It commits each fix atomically to preserve git history and generates a REVIEW-FIX.md summary of the outcomes.

The atomic commit workflow for automated code fixes works by committing each fix separately as the fixer agent processes findings in REVIEW.md. This approach preserves a clear git history and provides distinct rollback options for every individual change.

Yes, you can automate fixing all code review findings at once by using the --all and --auto flags. The --all flag broadens the fix scope, while --auto runs automated iterations on the REVIEW.md findings without manual intervention.

Yes, you need a REVIEW.md file containing the code review findings to automate code review fixes. The fixer agent reads this markdown file within a specified development phase to apply targeted changes and generate a phase-specific REVIEW-FIX.md summary.

The best way to track applied fixes in a phase-based development workflow is by generating a phase-specific REVIEW-FIX.md summary. This file documents the changes and outcomes after the fixer agent processes the REVIEW.md findings.