address-github-comments

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

Try it — you'd type

“Help me with address-github-comments.”

And you'd get back

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

Formatted for Claude, no fluff, no preamble.

Works the same way every time you ask.

Adding it takes about 30 seconds

Click Get this skill. Grab the .md file, one click, no account needed.

Add it to Claude. Drop it into ~/.claude/skills/. Claude picks it up the next time you open a session.

Ask normally. Type your question. The skill triggers on the right keywords — you don't have to remember anything.

Get this skill Unlock all skills — $25

You might also like

Smart Commit

Generate conventional commit messages by analyzing staged changes

Branch Cleanup

Find and delete merged/stale local and remote branches

Git Undo

Safely undo the last git operation (commit, merge, rebase, etc.)

Changelog Generator

Generate CHANGELOG.md from git history using conventional commits

Conflict Resolver

Analyze and suggest resolutions for merge conflicts

Git Bisect Helper

Automate git bisect to find the commit that introduced a bug

SKILL FILEWhat Claude actually reads

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