gh-address-comments

Fetch GitHub PR feedback threads and group them by file.

Updated Mar 24, 2026
One-click install
npx skills add https://github.com/pingqLIN/UniText --skill gh-address-comments-pingqlin
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: gh-address-comments
Source: https://github.com/pingqLIN/UniText/tree/main/runtime/skills/gh-address-comments
Command: npx skills add https://github.com/pingqLIN/UniText --skill gh-address-comments-pingqlin

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) components.

What problem does it solve?

Address actionable GitHub PR feedback by providing a deterministic workflow to fetch review threads, identify unresolved or conflicting comments, and prepare targeted fixes for a PR.

Core Features & Use Cases

  • Use the included Python script to fetch PR conversation comments, reviews, and inline threads for the current PR associated with the active branch.
  • Cluster actionable threads by file or behavior area, surface clear summaries, and guide users in selecting which threads to address.
  • Provide a safe, auditable edits workflow that maps each change back to the original feedback and enforces guardrails.

Quick Start

Run the fetch_comments.py script to retrieve all PR feedback for the current branch PR and start addressing actionable threads.

Frequently Asked Questions about gh-address-comments

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

FAQPage Schema
How do I address unresolved GitHub PR feedback systematically?

Address unresolved GitHub PR feedback by fetching review threads, grouping actionable comments by file, and guiding targeted fixes. The workflow surfaces unresolved threads on the current branch PR and maps each edit back to the original comment for auditable changes.

How do I group GitHub pull request review comments by file for fixes?

Group GitHub pull request review comments by file by running a Python script that fetches PR conversation comments, reviews, and inline threads. It clusters actionable threads by file or behavior area to prepare targeted fixes for the active branch PR.

Does this PR feedback workflow require GitHub CLI authentication?

Yes, this PR feedback workflow requires GitHub CLI authentication to fetch pull request data. The included Python script uses the GitHub CLI to retrieve conversation comments, reviews, and inline threads for the current branch PR safely and accurately.

Can I fetch inline review threads and conversation comments for the current branch PR?

You can fetch inline review threads and conversation comments for the current branch PR using the included Python script. It retrieves all PR feedback components, including reviews and inline threads, to identify unresolved or conflicting comments for resolution.

What is the best way to map code changes back to original GitHub PR comments?

The best way to map code changes back to original GitHub PR comments is through an auditable edits workflow with enforced guardrails. It tracks each modification to its source feedback thread, ensuring safe and traceable fixes across the pull request.

When should I not use an automated workflow for PR feedback resolution?

You should not use an automated workflow for PR feedback resolution when comments require subjective judgment or complex architectural decisions beyond simple fixes. The workflow is designed for actionable, targeted edits mapped directly to specific unresolved threads.