gh-address-comments

Fetch unresolved GitHub pull request review threads via GraphQL.

2|Updated Mar 29, 2026
One-click install
npx skills add https://github.com/NagyVikt/codex-plugins --skill gh-address-comments-nagyvikt
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: gh-address-comments
Source: https://github.com/NagyVikt/codex-plugins/tree/main/plugins/github/skills/gh-address-comments
Command: npx skills add https://github.com/NagyVikt/codex-plugins --skill gh-address-comments-nagyvikt

SYSTEM DOCUMENTATION & REQUIREMENTS

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

What problem does it solve?

This Skill solves the friction of managing GitHub pull request feedback by bridging the gap between flat comment surfaces and complex, thread-aware review states.

Core Features & Use Cases

  • Thread-Aware Inspection: Uses GraphQL to fetch unresolved review threads, inline comments, and resolution status that standard connectors miss.
  • Actionable Clustering: Automatically groups feedback by file or behavior, separating change requests from informational comments.
  • Traceable Implementation: Ensures code changes are directly linked to specific review threads, maintaining clear context for PR authors and reviewers.

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 address unresolved GitHub pull request review threads locally?

To address unresolved GitHub pull request review threads locally, use thread-aware comment analysis to fetch inline review locations via GraphQL and map the feedback to specific code changes in your local repository.

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

The best way to group actionable GitHub PR comments by file is to use automated clustering that separates change requests from informational comments, maintaining clear context for PR authors and reviewers.

Does this code review automation tool require GitHub CLI authentication?

Yes, this code review automation tool requires GitHub CLI authentication. It relies on the gh dependency to operate on active pull requests and fetch review states via GraphQL.

Can I map inline GitHub review feedback directly to local code changes?

Yes, you can map inline GitHub review feedback directly to local code changes. The skill integrates thread-aware inspection with local code implementation to ensure traceable fixes linked to specific threads.

Why does standard GitHub PR comment fetching miss unresolved thread states?

Standard GitHub PR comment fetching misses unresolved thread states because it uses flat comment surfaces, whereas thread-aware GraphQL inspection captures inline comments, review locations, and resolution status.