pr-address-comments

Summarize open GitHub Pull Request review threads and prompt for fixes.

17|2|Updated Mar 5, 2026
One-click install
npx skills add https://github.com/DavidLiuXh/jarvis-personal-ai --skill pr-address-comments-davidliuxh
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: pr-address-comments
Source: https://github.com/DavidLiuXh/jarvis-personal-ai/tree/main/.gemini/skills/pr-address-comments
Command: npx skills add https://github.com/DavidLiuXh/jarvis-personal-ai --skill pr-address-comments-davidliuxh

SYSTEM DOCUMENTATION & REQUIREMENTS

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

What problem does it solve?

It helps you quickly understand and address outstanding feedback on your current GitHub Pull Request so you can move it forward.

Core Features & Use Cases

  • PR-wide feedback summarization: Aggregates general comments and reviews to highlight what still needs attention.
  • Inline thread reconstruction: Groups review replies into threaded discussions with line/file ranges for faster triage.
  • User-guided next steps: Produces a clear status summary and prompts you to decide what to fix or skip rather than auto-applying changes.
  • Weed out irrelevant automation: Ignores known boilerplate review messages to focus on actionable feedback.

Quick Start

Ask the assistant to run the pr-address-comments skill to summarize the open GitHub PR comment threads for your current branch and tell you what to address next.

Frequently Asked Questions about pr-address-comments

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

FAQPage Schema
How do I triage outstanding GitHub pull request comments for my current branch?

To triage GitHub pull request comments, the Skill fetches PR data via gh and node scripts, reconstructs inline review threads with file ranges, and summarizes open versus resolved items with numbered references for user-guided fixes.

What is the best way to summarize open GitHub PR review threads before updating code?

Summarizing open GitHub PR review threads involves aggregating general comments and inline discussions, filtering out boilerplate automation messages, and presenting a clear status summary so you can decide what to address or skip.

Do I need gh and node installed to resolve GitHub PR comment threads?

Yes, resolving GitHub PR comment threads requires gh, node, and git installed, because the Skill executes scripts/fetch-pr-info.js to retrieve PR metadata and reconstruct threaded feedback discussions for your current branch.

Can I automatically apply code changes to fix GitHub PR review feedback?

No, you cannot automatically apply code changes, because the Skill explicitly avoids automatic edits and instead prompts you to decide what to fix or skip after presenting the summarized open comment threads.

How does comment triage handle irrelevant automated review messages on GitHub?

Comment triage handles irrelevant automated messages by ignoring known boilerplate review messages, focusing only on actionable feedback to produce a clear status summary of what still needs attention on your pull request.