kramme:resolve-review

To automatically resolve code review findings, you can use a workflow that reads review context from PRs, generates fixes, and outputs a patch. This Skill automates that process and creates a REVIEW_OVERVIEW.md detailing the actions taken.

The best way to document code review fixes is to generate a REVIEW_OVERVIEW.md file outlining findings, decisions, and changes. This Skill automatically creates this documentation while applying fixes derived from review comments.

Yes, you can apply safe fixes and generate patch notes from multiple PR review comments. This Skill reads the review context, applies deterministic fixes, and outputs an overview document detailing all findings and actions.

No, this code review resolution workflow does not require any dependencies or external components. It operates independently to read review context, implement fixes, and generate documentation for Git repositories.

You need to generate a REVIEW_OVERVIEW.md when you want a clear record of code review findings, decisions, and applied changes. It is useful after receiving multiple review comments on a PR or merged changes.

An automated workflow for code review findings ensures deterministic fixes and consistent documentation. It saves time by automatically reading review context, applying safe fixes, and detailing all actions in a patch note and overview file.