gh-address-comments

Fetch GitHub pull request review threads and implement selected fixes locally.

Updated Apr 14, 2026
One-click install
npx skills add https://github.com/dallay/opencode-docker --skill gh-address-comments-dallay
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: gh-address-comments
Source: https://github.com/dallay/opencode-docker/tree/main/config/skills/gh-address-comments
Command: npx skills add https://github.com/dallay/opencode-docker --skill gh-address-comments-dallay

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) components.

What problem does it solve?

This Skill helps developers inspect and act on GitHub pull request review feedback that the standard connector surfaces only as flat comments, surfacing thread-aware review context and grouping actionable threads for targeted fixes.

Core Features & Use Cases

  • Thread-aware fetching: Uses a bundled GraphQL workflow to retrieve reviewThreads, resolution state, and inline anchors that the connector does not preserve.
  • Actionable clustering: Groups comments by file or behavioral area and separates change requests from informational notes or duplicates.
  • Local implementation workflow: Guides confirmation, implements selected fixes locally, and summarizes which threads were addressed versus left open.
  • Use Case: When a developer wants to work through unresolved review threads on the current branch PR, fetch thread context, and apply a curated set of fixes locally before summarizing results.

Quick Start

Use the gh-address-comments skill to fetch thread-aware review context for the current branch PR, pick which unresolved actionable threads to fix, and implement the selected changes locally.

Frequently Asked Questions about gh-address-comments

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

FAQPage Schema
How do I fetch unresolved GitHub pull request review threads with full context?

To fetch unresolved GitHub pull request review threads with full context, this Skill uses a bundled GraphQL script via gh CLI to retrieve reviewThreads, resolution state, and inline anchors that standard flat comment reads do not preserve. It groups actionable feedback by file or area for targeted local implementation.

What is the best way to group actionable PR review comments for local fixes?

The best way to group actionable PR review comments for local fixes is to cluster them by file or behavioral area, separating change requests from informational notes. This Skill fetches thread-aware context and guides implementation of selected fixes locally before summarizing resolved threads.

Do I need gh CLI authentication to read GitHub review threads?

Yes, you need gh CLI authentication to read GitHub review threads. This Skill requires gh CLI authentication to invoke the bundled gh api GraphQL script for thread-aware data, alongside the configured GitHub integration for flat comment reads.

Can I separate change requests from informational notes in GitHub PR comments?

Yes, you can separate change requests from informational notes in GitHub PR comments. This Skill performs actionable clustering to group comments by file or behavioral area, distinguishing actionable change requests from informational notes or duplicates for focused local implementation.

Does the GitHub connector preserve review thread resolution state and inline anchors?

No, the standard GitHub connector surfaces PR comments only as flat comments and does not preserve review thread resolution state or inline anchors. This Skill uses a bundled GraphQL workflow to retrieve that thread-level context.

How do I implement selected fixes from unresolved PR review threads locally?

To implement selected fixes from unresolved PR review threads locally, this Skill guides confirmation of actionable threads, applies the curated changes to your local branch, and summarizes which threads were addressed versus left open.