pr-feedback-addresser

Plan and apply code changes for PR review comments with RuboCop and tests.

Updated Jan 15, 2026
One-click install
npx skills add https://github.com/lutzcc1/claude-skills --skill pr-feedback-addresser
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: pr-feedback-addresser
Source: https://github.com/lutzcc1/claude-skills/tree/main/project/pr-feedback-addresser
Command: npx skills add https://github.com/lutzcc1/claude-skills --skill pr-feedback-addresser

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill streamlines the process of addressing PR feedback by systematically planning and applying code changes, ensuring quality and consistency with Sprout's Rails conventions.

Core Features & Use Cases

  • Organized review: Groups PR comments by file and line number to clarify what needs to change.
  • Structured attack plans: For each comment, builds a clear, actionable plan and applies changes following Sprout conventions.
  • Quality verification: Runs RuboCop on changed files and executes relevant tests to ensure no regressions.

Quick Start

Fetch the current PR with gh pr view --json number,title,url,comments,reviewThreads,files, then parse and address comments, run rubocop on changed files, and execute the appropriate Rails tests to verify changes. Summarize and prepare for commit after user approval.

Frequently Asked Questions about pr-feedback-addresser

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

FAQPage Schema
How do I automatically address pull request review comments in a Rails project?

To address pull request review comments automatically, this Skill parses PR feedback via the gh CLI, groups comments by file and line, and applies targeted code changes to resolve them in your Rails project.

Can I run RuboCop and tests automatically after fixing PR review feedback?

Yes, you can run RuboCop and tests automatically after fixing PR review feedback, as this Skill executes RuboCop on changed files and runs relevant Rails test suites to verify no regressions occur.

What's the best way to systematically plan code changes from GitHub PR comments?

The best way to systematically plan code changes from GitHub PR comments is to group them by file and line number, then build a structured attack plan for each comment before applying the modifications.

Do I need the gh CLI installed to automate addressing GitHub PR review comments?

Yes, you need the gh CLI installed to automate addressing GitHub PR review comments, because this Skill relies on the gh pr view command to fetch PR metadata including comments, review threads, and files.

Does this automated PR feedback resolver work outside of Rails environments?

This automated PR feedback resolver is designed for Rails environments and requires a Rails project setup with RuboCop and test suites to execute its quality verification checks properly.

What limitations exist when using an automated tool to fix PR review comments?

A key limitation when using an automated tool to fix PR review comments is that it requires specific environment dependencies like the gh CLI, a Rails project, and RuboCop, meaning it cannot operate in non-Rails or CLI-less setups.