addressing-pr-feedback

Fetch GitHub PR review comments, group them by reviewer type, and summarize feedback.

2|Updated Jan 29, 2026
One-click install
npx skills add https://github.com/oryanmoshe/agent-skills --skill addressing-pr-feedback
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: addressing-pr-feedback
Source: https://github.com/oryanmoshe/agent-skills/tree/main/skills/addressing-pr-feedback
Command: npx skills add https://github.com/oryanmoshe/agent-skills --skill addressing-pr-feedback

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This skill helps teams tackle GitHub pull request feedback by automatically fetching review comments, distinguishing human feedback from bot suggestions, and guiding you to address the most critical issues.

Core Features & Use Cases

  • Fetch all PR comments (human and bot) and present a structured summary.
  • Group comments by reviewer type and flag outdated items when code changes.
  • Provide an interactive selection flow to apply fixes and respond to comments.
  • Use Case: during code reviews, quickly understand reviewer intent and craft precise responses.

Quick Start

Ask me to address PR feedback for the current pull request to fetch comments, summarize them, and present options to apply fixes.

Frequently Asked Questions about addressing-pr-feedback

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

FAQPage Schema
How do I automatically fetch and address GitHub PR review feedback?

You can fetch and address GitHub PR review feedback automatically by using a skill that identifies the relevant PR from your current branch, retrieves all comments, and groups them by reviewer type for selection. It presents a structured summary to guide applying fixes.

Can I separate human reviewer comments from bot suggestions on a pull request?

Yes, separating human reviewer comments from bot suggestions is possible. The skill fetches all comments, distinguishes human feedback from bot suggestions, and groups them by reviewer type to help you prioritize addressing critical issues.

How do I handle outdated PR review comments after code changes?

Handling outdated PR review comments after code changes is managed by the skill's robust tracking. It automatically flags outdated items when code changes occur, ensuring you do not waste time addressing feedback that no longer applies to the current state.

What do I need to fetch pull request comments from my current branch?

To fetch pull request comments from your current branch, you need the GitHub CLI tooling installed and appropriate PR access. The skill uses these dependencies to identify the relevant PR and retrieve all review comments.

What is the best way to group and resolve multiple GitHub code review comments?

The best way to group and resolve multiple GitHub code review comments is using an automated workflow that organizes feedback by reviewer type. This provides an interactive selection flow to apply fixes and craft precise responses directly.

Does addressing PR feedback work without direct GitHub CLI integration?

Addressing PR feedback does not work without GitHub CLI integration, because the skill requires GH CLI tooling to identify the relevant PR and fetch all comments from your current branch.