Skip to main content
NEW · APP STORE Now on iOS · macOS · iPad Android & Windows soon GET IT
Prompts GitHub PR Comment Resolver with gh CLI

agent coding skill risk: medium

GitHub PR Comment Resolver with gh CLI

Provides a workflow for using the gh CLI to fetch, categorize, fix, and respond to review or issue comments on an open GitHub Pull Request.

  • External action: high

SKILL 1 file

SKILL.md
---
name: antigravity-awesome-skills-address-github-comments
description: "Use when you need to address review or issue comments on an open GitHub Pull Request using the gh CLI."
---
# 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.

REQUIRED CONTEXT

  • current branch's open PR
  • gh CLI authentication

TOOLS REQUIRED

  • gh

ROLES & RULES

  1. Always read the surrounding code of a comment.
  2. Check gh auth status before starting.
  3. Wait for user confirmation on which comments to address first if there are many.
  4. Use this skill only when the task clearly matches the scope described above.
  5. Do not treat the output as a substitute for environment-specific validation, testing, or expert review.
  6. Stop and ask for clarification if required inputs, permissions, safety boundaries, or success criteria are missing.

EXPECTED OUTPUT

Format
markdown
Constraints
  • include workflow steps
  • list prerequisites and common mistakes
  • wait for user confirmation before applying fixes

FAILURE MODES

  • May apply fixes without understanding context.
  • May skip auth verification.

CAVEATS

Dependencies
  • Requires gh CLI authenticated.
Missing context
  • How PR_NUMBER or current branch is determined when not explicit.
  • Exact format expected for categorized comment plans or responses.
Ambiguities
  • 'Or use a custom script if available to list threads.' does not specify the script or conditions.
  • 'Wait for user confirmation' does not specify the interaction mechanism or format.

QUALITY

OVERALL
0.78
CLARITY
0.85
SPECIFICITY
0.70
REUSABILITY
0.80
COMPLETENESS
0.75

IMPROVEMENT SUGGESTIONS

  • Add explicit placeholders (e.g., {{PR_NUMBER}}, {{BRANCH}}) for reusability.
  • Define a required output schema for the 'Categorize and Plan' step.

USAGE

Copy the prompt above and paste it into your AI of choice — Claude, ChatGPT, Gemini, or anywhere else you're working. Replace any placeholder sections with your own context, then ask for the output.

MORE FOR AGENT