dev6-review-fix

Automating code review fixes involves reading review notes and PRD files, triaging comments by severity, applying targeted code changes across referenced files, running the test suite to verify regressions, and staging a git commit with a standardized message before triggering a pull request workflow.

Triage and prioritize code review comments by classifying them into Critical, Suggestion, and Nit categories to focus development effort on correctness and security first, then applying targeted fixes to the referenced files based on the feature intent documented in the PRD.

To run tests and stage a git commit after applying fixes, execute the available test suite to detect regressions, stage the modified code changes in git, and create a commit with a standardized message that hands off to the subsequent pull request workflow step.

Applying code review fixes without a test suite is supported by staging and committing changes directly, although running the test suite when available is required to detect regressions and verify correctness before creating the final git commit.

Repository access is required to automate code review fix workflows because the process needs permission to read and edit files, run the test suite, stage code changes, and create a git commit before invoking the subsequent pull request workflow step.