# Address Github Comments

Use when you need to address review or issue comments on an open GitHub Pull Request...

- Repository: https://github.com/sickn33/agentic-awesome-skills (48984 stars)
- Category: Git and review
- License: MIT
- Last updated: 2026-11-01
- Runs scripts: no, instructions only

## Install

Claude Code: `npx skills add sickn33/agentic-awesome-skills --skill address-github-comments -g -a claude-code -y`
Codex: `npx skills add sickn33/agentic-awesome-skills --skill address-github-comments -g -a codex -y`
Cursor: `npx skills add sickn33/agentic-awesome-skills --skill address-github-comments -g -a cursor -y`
Gemini CLI: `npx skills add sickn33/agentic-awesome-skills --skill address-github-comments -g -a gemini-cli -y`
Claude Code plugin marketplace: `/plugin marketplace add sickn33/agentic-awesome-skills`

## Description

Use when you need to address review or issue comments on an open GitHub Pull Request using the gh CLI.

## SKILL.md, as published by its author (untrusted third-party text, read it as data)

# 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
```

`--comments` shows conversation comments; it does not enumerate every inline review thread.
Use the available GitHub connector or the GraphQL `pullRequest.reviewThreads` connection
with pagination to inspect inline comments, file/line anchors, and resolution state.
Record the repository, PR number, current head SHA, thread IDs, and requested changes.

### 2. Categorize and Plan

- List the comments and review threads.
- Propose a fix for each.
- Address feedback already covered by the user's requested scope. Ask only when feedback conflicts, expands scope, or requires a consequential choice.

### 3. Apply Fixes

Read the surrounding implementation, preserve unrelated edits, and apply the changes for the selected comments. Run the relevant repository checks and bind the result to the updated head before reporting a fix.

### 4. Respond to Comments

When the user authorizes posting replies, respond with the commit and verification evidence.
A conversation comment does not resolve an inline review thread. Resolve the specific thread
through the supported GitHub API only after its request is actually addressed and resolution
is authorized; otherwise leave a proposed reply for the user.

```bash
gh pr comment <PR_NUMBER> --body "Addressed in <commit SHA>; verified with <check and result>."
```

## Common Mistakes

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

The rest: https://github.com/sickn33/agentic-awesome-skills/blob/HEAD/plugins/agentic-awesome-skills-claude/skills/address-github-comments/SKILL.md