Address GitHub Comments Skill · Devops

Address GitHub Comments with gh CLI

Stop wasting time on PRs.

Use this 4-step GitHub CLI workflow to resolve review comments efficiently. Automate your feedback loop today!

  • GitHub CLI
  • Pull Requests
  • Code Review
  • DevOps Workflow
  • Git

About This Skill

Streamline your PR process with a 4-step workflow that leverages the GitHub CLI to inspect, plan, apply, and respond to review comments systematically.

Quick Start

  1. 1Authenticate using 'gh auth login'
  2. 2Fetch PR comments with 'gh pr view --comments'
  3. 3Respond to resolved threads using 'gh pr comment'
Example Command
gh pr comment <PR_NUMBER> --body "Addressed in latest commit."

Core Capabilities

Inspect Comments

Fetch and review all PR comments and issue feedback using the GitHub CLI to ensure no feedback is missed.

Categorize and Plan

Systematically list review threads and propose specific fixes for each item before implementation.

Apply Fixes

Execute precise code changes based on the planned resolutions for each identified comment.

Respond to Comments

Mark threads as resolved by posting responses directly to the PR via the gh CLI.

Usage Examples

Input

Check the comments on my current PR.

Output

Running 'gh pr view --comments' to retrieve all active feedback threads for your current branch.

Input

I've fixed the naming convention issue in PR #123.

Output

Executing 'gh pr comment 123 --body "Addressed in latest commit."' to notify the reviewer.

Before

PR #45 has 3 unresolved comments regarding variable naming and error handling.

After

All 3 comments addressed with code changes and marked as resolved via gh CLI.

SKILL.md

---
name: address-github-comments
description: "Use when you need to address review or issue comments on an open GitHub Pull Request using the gh CLI."
risk: unknown
source: community
date_added: "2026-02-27"
---

# Address GitHub Comments

## Overview

Efficiently address PR review comments or issue feedback using the GitHub CLI (`gh`). This skill ensures all feedback is addressed systematically.

## Prerequisites

Ensure `gh` is authenticated.

```bash
gh auth status
```

If not logged in, run `gh auth login`.

## Workflow

### 1. Inspect Comments

Fetch the comments for the current branch's PR.

```bash
gh pr view --comments
```

Or use a custom script if available to list threads.

### 2. Categorize and Plan

- List the comments and review threads.
- Propose a fix for each.
- **Wait for user confirmation** on which comments to address first if there are many.

### 3. Apply Fixes

Apply the code changes for the selected comments.

### 4. Respond to Comments

Once fixed, respond to the threads as resolved.

```bash
gh pr comment <PR_NUMBER> --body "Addressed in latest commit."
```

## Common Mistakes

- **Applying fixes without understanding context**: Always read the surrounding code of a comment.
- **Not verifying auth**: Check `gh auth status` before starting.

## When to Use
This skill is applicable to execute the workflow or actions described in the overview.

## Limitations
- Use this skill only when the task clearly matches the scope described above.
- Do not treat the output as a substitute for environment-specific validation, testing, or expert review.
- Stop and ask for clarification if required inputs, permissions, safety boundaries, or success criteria are missing.

Frequently Asked Questions

FAQ

Which tools are compatible with this skill?
This skill requires the GitHub CLI (gh) installed and a valid authentication token configured on your system.
Who is the target audience for this skill?
It is designed for developers, software engineers, and DevOps practitioners who manage code reviews via GitHub.
How does this differ from using the GitHub Web UI?
It enables a terminal-centric workflow, allowing developers to stay in their IDE and use scripts to handle repetitive response patterns.
Does this support multiple programming languages?
Yes, because it operates at the CLI and PR level, it is language-agnostic and works for any project hosted on GitHub.
What are the expected results after using this skill?
The result is a systematically addressed set of PR comments with corresponding code fixes and resolution notifications sent to reviewers.

Discussion

Discussion

0 comments
U

Trigger Phrases

Use these phrases to activate this skill in your AI coding assistant:

address github commentsresolve pr feedbackuse gh cli for commentsrespond to github reviewfix pr comments