Skip to content
Back to skills

Gh Reply Review Comment

ASecurity

Reply to PR review comments using the correct GitHub API endpoint. Use when responding to inline code review feedback (not gh pr comment).

  • 666 stars
  • 0 votes
  • 0 copies
  • 2 views
  • Added February 8, 2026
documentationgobashgitapi

Works with

  • api

Security analysis

A100/100

Scanned February 12, 2026

npx -y skills add majiayu000/claude-skill-registry --skill gh-reply-review-comment --agent claude-code

Installs into .claude/skills of the current project.

Are you the author of Gh Reply Review Comment?

Add the live security badge to your README. It updates with every re-scan.

Security grade badge for Gh Reply Review Comment
[![Security: A — Skills Directory](https://www.skillsdirectory.com/api/skills/majiayu000-gh-reply-review-comment/badge)](https://www.skillsdirectory.com/skills/majiayu000-gh-reply-review-comment)

More formats (shields.io, HTML) on the badges page. Keep it an A: scan every change in CI with Pro.

Download with Pro
SKILL.md
---
name: gh-reply-review-comment
description: "Reply to PR review comments using the correct GitHub API endpoint. Use when responding to inline code review feedback (not gh pr comment)."
category: github
agent: test-engineer
user-invocable: false
---

# Reply to Review Comments

Reply to PR review comments using the correct GitHub API.

## When to Use

- Responding to inline code review feedback
- Addressing specific review comments
- Confirming fixes have been implemented
- Updating reviewers on progress

## Critical: Two Types of Comments

**DO NOT confuse these**:

1. **PR-level comments** (general timeline): `gh pr comment`
2. **Review comment replies** (inline code): GitHub API (see below)

## Quick Reference

```bash
# 1. Get comment ID
gh api repos/OWNER/REPO/pulls/PR/comments \
  --jq '.[] | {id: .id, path: .path, body: .body}'

# 2. Reply to comment
gh api repos/OWNER/REPO/pulls/PR/comments/COMMENT_ID/replies \
  --method POST -f body="✅ Fixed - brief description"

# 3. Verify reply posted
gh api repos/OWNER/REPO/pulls/PR/comments \
  --jq '.[] | select(.in_reply_to_id)'
```

## Workflow

1. **Get comment IDs**: List all review comments
2. **Apply fixes**: Make the requested changes
3. **Reply to EACH comment**: Respond individually to each
4. **Verify replies**: Check they all posted successfully
5. **Monitor CI**: Ensure changes pass CI

## Reply Format

Keep responses SHORT and CONCISE (1 line preferred):

**Good examples**:

- `✅ Fixed - Updated conftest.py to use real repository root`
- `✅ Fixed - Deleted test file as requested`
- `✅ Fixed - Removed markdown linting section`

**Bad examples**:

- Long explanations
- Defensive responses
- Multiple paragraphs

## Error Handling

| Problem | Solution |
|---------|----------|
| Comment ID invalid | Verify using API call |
| Permission denied | Check `gh auth status` |
| Reply fails | Verify PR and comment exist |
| Comment not found | Double-check ID format |

## Verification

After replying:

```bash
# Check replies appeared
gh api repos/OWNER/REPO/pulls/PR/comments \
  --jq '.[] | select(.in_reply_to_id) | {id: .id, body: .body}'

# Verify CI status
gh pr checks PR
```

## References

- See CLAUDE.md for complete PR workflow
- See `/agents/guides/github-review-comments.md` for detailed guide

Attribution

Is this your skill, or is something wrong with this listing? Request removal or report an issue. Author removals are honored within 72 hours.

Comments

Loading comments…

Newsletter

Get the weekly list of safe new skills, and the ones we pulled.