fix-pr-comments

To automatically fix unresolved GitHub PR review comments, use this Skill to fetch PR data, analyze inline code comments and review notes, then batch and push changes. It maps each comment to exact file lines and applies fixes using MultiEdit workflows.

Yes, you need the gh CLI and git tooling to automate PR review fixes. This Skill requires both tools to fetch pull request data from GitHub repositories and to commit and push the requested code changes back to the remote branch.

Batching code review fixes per file with MultiEdit works by analyzing all requested PR changes, grouping them by target file, and applying multiple edits in a single operation. This minimizes file churn and generates a cohesive patch for commit and push.

Yes, you can apply GitHub pull request review changes across multiple files automatically. The Skill analyzes all inline discussion and review notes, batches the requested edits per file, and pushes a single cohesive patch using conventional commits.

The best way to avoid unrelated changes when automating PR fixes is to use guardrails that preserve original context. This Skill strictly applies only reviewer-requested modifications and commits them using conventional commit messages.

Limitations of automating GitHub code review fixes include dependency on the gh and git tooling, and the requirement for a valid GitHub repository with open pull requests. It handles inline code comments and review notes but avoids unrelated changes to preserve context.