gh-address-comments

Fetch and manage GitHub pull request review comments using the GitHub CLI.

Updated Jul 6, 2026
One-click install
npx skills add https://github.com/shirulot/codex-skill --skill gh-address-comments-shirulot
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: gh-address-comments
Source: https://github.com/shirulot/codex-skill/tree/main/gh-address-comments
Command: npx skills add https://github.com/shirulot/codex-skill --skill gh-address-comments-shirulot

SYSTEM DOCUMENTATION & REQUIREMENTS

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

What problem does it solve?

This Skill automates the tedious process of identifying, tracking, and addressing feedback on GitHub pull requests, ensuring no review comments are overlooked.

Core Features & Use Cases

  • Comment Aggregation: Fetches all conversation comments, review submissions, and inline review threads from an open PR.
  • Interactive Workflow: Provides a structured way to review and address specific feedback threads directly from the CLI.
  • Use Case: When a PR receives multiple rounds of feedback across different files, use this Skill to consolidate all pending items into a single list to systematically resolve them.

Quick Start

Run the gh-address-comments skill to fetch and display all pending review comments for the current branch.

Frequently Asked Questions about gh-address-comments

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

FAQPage Schema
How do I retrieve and resolve GitHub pull request review comments from the CLI?

You can retrieve and resolve GitHub pull request review comments by automating the fetching of conversation comments, review submissions, and inline threads directly through the GitHub CLI.

What is the best way to track pending code review feedback across multiple files in a pull request?

Tracking pending code review feedback is best handled by consolidating all conversation comments and inline review threads from an open PR into a single, structured list for systematic resolution.

Do I need the GitHub CLI to manage and address PR review threads?

Yes, you need the GitHub CLI (gh) installed and authenticated with appropriate repository and workflow scopes to manage and address PR review threads effectively.

Can I aggregate all inline code review threads for an open pull request into one list?

Yes, you can aggregate all inline code review threads, conversation comments, and review submissions for an open pull request into a consolidated list to ensure no feedback is overlooked.

Does this GitHub CLI automation work for tracking feedback across multiple review rounds?

Yes, this GitHub CLI automation works for tracking feedback across multiple review rounds, providing an interactive workflow to systematically address specific feedback threads from the CLI.