fix-pr-comments

Apply GitHub PR review comments as batched file edits and push a commit.

Updated Aug 23, 2026
One-click install
npx skills add https://github.com/cedricfressin/claude-config --skill fix-pr-comments
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: fix-pr-comments
Source: https://github.com/cedricfressin/claude-config/tree/main/skills/git-fix-pr-comments
Command: npx skills add https://github.com/cedricfressin/claude-config --skill fix-pr-comments

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill automates the tedious process of addressing GitHub PR review feedback by fetching unresolved comments and applying the requested changes across the codebase, then preparing a clean commit for review.

Core Features & Use Cases

  • Automated comment gathering: Collect CHANGES_REQUESTED and inline review comments from a PR.
  • Deterministic edits by file: Batch edits per file to produce coherent patches and minimize drift.
  • Commit & push: Create a descriptive commit and push updates to the PR branch.
  • Use Case: When a PR has multiple review comments across several files, this Skill applies all changes and pushes a single, coherent commit.

Quick Start

Example: Run the skill on a PR with CHANGES_REQUESTED comments to apply the requested edits and push a commit.

Frequently Asked Questions about fix-pr-comments

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I automatically fix pull request review comments on GitHub?

Automatically fixing pull request review comments involves fetching unresolved CHANGES_REQUESTED notes and inline feedback, then batching edits per file to apply all requested changes and push a clean commit back to the PR branch.

How do I batch code review edits across multiple files in a single commit?

Batching code review edits across multiple files requires grouping all requested changes by file to produce coherent patches, minimizing drift, and staging them into a single descriptive commit before pushing to the PR branch.

Can I apply CHANGES_REQUESTED comments without modifying unrelated code?

Applying CHANGES_REQUESTED comments without modifying unrelated code is possible by identifying specific inline review notes and ensuring edits are strictly batched per file, leaving all other changes untouched.

What tools are needed to automate addressing PR review feedback with Git?

Automating PR review feedback addressing requires Read, Edit, and MultiEdit tooling for applying codebase changes, plus standard Git commands to stage, commit with a descriptive message, and push updates to the PR branch.

Does automating PR comment fixes work for PRs with feedback across several files?

Automating PR comment fixes works for PRs with feedback across several files by collecting all unresolved comments, applying the requested edits per file, and pushing a single coherent commit to the PR branch.