pr-comments

Aggregate GitHub PR comments and review feedback for the current branch.

1|Updated May 13, 2018
One-click install
npx skills add https://github.com/hujw77/dotfiles --skill pr-comments-hujw77
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: pr-comments
Source: https://github.com/hujw77/dotfiles/tree/main/home/.config/claude/skills/pr-comments
Command: npx skills add https://github.com/hujw77/dotfiles --skill pr-comments-hujw77

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill requires gh, jq, and includes scripts (resource) components.

What problem does it solve?

PR feedback tends to be scattered across comments, inline reviews, and overall reviews. This Skill aggregates all feedback for the current branch, presenting it for interactive resolution to speed up PR closure.

Core Features & Use Cases

  • Gather general PR comments, inline review comments, and reviewer decisions for a given branch.
  • Present each item with context and actionable options to fix, skip, or request more information.
  • Use case: a maintainer wants to address all feedback before merging a PR on a busy project.

Quick Start

Run the fetch-pr-feedback.sh script to collect PR feedback for the current branch.

Frequently Asked Questions about pr-comments

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

FAQPage Schema
How do I aggregate all GitHub PR comments for a branch into one view?

You can aggregate GitHub PR comments by running a script to gather general comments, inline reviews, and reviewer decisions for the current branch into a single structured output. This consolidates scattered feedback for interactive processing.

What is interactive PR review and how does it handle inline feedback?

Interactive PR review identifies and summarizes all feedback for a branch, presenting inline comments and reviewer decisions with actionable options to fix, skip, or request more information. It streamlines resolving scattered code review items.

Does this PR feedback aggregation require the GitHub CLI and jq?

Yes, gathering and structuring pull request feedback through this approach requires the GitHub CLI and jq to query the gh API and parse responses for interactive resolution.

What's the best way to resolve multiple reviewer comments on a GitHub pull request?

The best way to resolve multiple reviewer comments is to aggregate all general, inline, and review feedback for the branch, then interactively process each item with options to fix, skip, or ask for clarification to speed up PR closure.

Can I collect pull request feedback across multiple files and reviewers?

Yes, this process collects pull request feedback across multiple files and reviewers for a given branch. It handles general, inline, and review comments, outputting structured feedback suitable for interactive resolution.

When should I not use a script to summarize GitHub PR comments?

You should not use a script to summarize GitHub PR comments if your repository is not hosted on GitHub or if you lack the required GitHub CLI and jq dependencies, as it relies specifically on the gh API for feedback extraction.