gh-address-comments

Fetch and cluster unresolved GitHub pull request review threads and inline comments.

4|Updated Jun 10, 2026
One-click install
npx skills add https://github.com/mymx2/foreman --skill gh-address-comments-mymx2
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: gh-address-comments
Source: https://github.com/mymx2/foreman/tree/main/.agents/skills/gh-address-comments
Command: npx skills add https://github.com/mymx2/foreman --skill gh-address-comments-mymx2

SYSTEM DOCUMENTATION & REQUIREMENTS

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

What problem does it solve?

This skill solves the issue of fragmented and incomplete visibility into GitHub pull request review threads, allowing you to systematically address actionable feedback without missing inline comments or resolution states.

Core Features & Use Cases

  • Thread-Aware Inspection: Fetches unresolved review threads, inline comments, and resolution status that standard PR connectors often miss.
  • Actionable Clustering: Groups feedback by file or behavior, separating critical change requests from informational comments.
  • Use Case: When a reviewer leaves multiple inline comments across several files, use this skill to aggregate them into a clear, prioritized checklist for implementation.

Quick Start

Use the gh-address-comments skill to fetch all unresolved review threads for the current pull request and guide me through implementing the necessary fixes.

Frequently Asked Questions about gh-address-comments

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

FAQPage Schema
How do I resolve unresolved GitHub pull request review threads programmatically?

You can resolve unresolved GitHub pull request review threads by fetching and clustering inline comments via the GitHub CLI. This aggregates fragmented PR feedback into a prioritized checklist of actionable code changes.

How do I fetch all inline comments from a GitHub PR review?

To fetch all inline comments from a GitHub PR review, you need thread-aware inspection that queries GraphQL via the GitHub CLI. This identifies specific code changes, resolution states, and review context across your active pull requests.

Do I need the GitHub CLI to fetch pull request review comments?

Yes, you need the GitHub CLI installed and authenticated access to the repository to fetch pull request review comments. The tool relies on gh to perform thread-aware analysis and retrieve unresolved review threads.

What is the best way to group GitHub PR feedback by file?

The best way to group GitHub PR feedback by file is through actionable clustering, which separates critical change requests from informational comments. This creates a clear, prioritized checklist for implementing necessary fixes across multiple files.

Why does my PR connector miss unresolved inline comments on GitHub?

Standard PR connectors often miss unresolved inline comments because they lack thread-aware inspection. Fetching complete review context and resolution states requires querying the GitHub API specifically for unresolved review threads.