Skip to content
Skills Library
Programming · Writing

reply

/reply

This skill should be used when the user asks to "reply to PR comments", "respond to review comments", "reply to PR #123", "answer PR feedback", or wants to respond to unresolved review threads or comments from other users on a pull request.

Licence
MIT
Last repository change
16.07.2026

Assessment and security

84/ 100Class: good
Format9 / 25
Frontmatter with name and description, valid name, description up to 1,024 characters, name matching the folder.
Discoverability25 / 25
Description explains when to use the skill, has a reasonable length and uses third person.
Content35 / 35
At least 150 words and at most 500 lines, headings, step lists, examples or code.
Hygiene15 / 15
No placeholders such as TODO, no Windows paths, with a licence.
Riskno signals detected in the scan
Files in this package
1
Scripts
0
HTML comments
0
URLs in SKILL.md
0
Deprecation

No signals detected. Repository changed on 16.07.2026, without references to retired models or APIs.

Licence

MIT, open: use and modify while retaining author attribution.

What it does and when to use it

This skill should be used when the user asks to "reply to PR comments", "respond to review comments", "reply to PR #123", "answer PR feedback", or wants to respond to unresolved review threads or comments from other users on a pull request.

Triggers from the description

reply to PR commentsrespond to review commentsreply to PR #123answer PR feedback

Arguments

/reply <pr-number>
Original author description

This skill should be used when the user asks to "reply to PR comments", "respond to review comments", "reply to PR #123", "answer PR feedback", or wants to respond to unresolved review threads or comments from other users on a pull request.

How it works

  1. Helper Scripts
  2. Workflow
  3. Important Guidelines
  4. Script Reference
Original SKILL.md headings · 156 lines, 720 words
SKILL.md preview
---
description: This skill should be used when the user asks to "reply to PR comments", "respond to review comments", "reply to PR #123", "answer PR feedback", or wants to respond to unresolved review threads or comments from other users on a pull request.
argument-hint: "<pr-number>"
disable-model-invocation: true
allowed-tools: Bash, Read, Write, Grep, Glob
---

# GitHub PR Comment Replier

Reply to comments on a GitHub pull request by finding threads that need responses, generating thoughtful replies based on codebase context, and posting them directly.

**Filter criteria for actionable threads:**
- Thread is **not resolved**
- Latest comment was **not generated by this skill** (detected by "github-devflow:reply" signature)

## Helper Scripts

This skill uses shared helper scripts in `scripts/` at the plugin root:

| Script | Purpose |
|--------|---------|
| `fetch-review-threads.sh` | Fetch review threads from a PR with optional filtering |
| `post-reply.sh` | Post a reply to a review thread |

## Workflow

### Step 1: Fetch Actionable Threads

Use the helper script to fetch review threads that need replies:

```bash
PR_NUMBER=$ARGUMENTS
bash ${CLAUDE_PLUGIN_ROOT}/scripts/fetch-review-threads.sh $PR_NUMBER --filter-resolved --filter-skill reply
```

This returns JSON with:
- `owner`, `repo`, `prNumber`: Repository context
- `threads`: Array of threads requiring action
- `totalCount`: Number of actionable threads

Each thread contains:
- `id`: Thread ID for posting replies (e.g., `PRRT_xxx`)
- `isResolved`: Always `false` (filtered)
- `path`: File path in the repository
- `line`: Line number in the file
- `comments.nodes`: Array of all comments in the thread (latest comment is last)

If no actionable threads are found (`totalCount: 0`), report that no replies are needed.

### Step 2: Analyze and Generate Replies

For each actionable thread:

1. **Read all comments**: Parse the entire `comments.nodes` array to understand the full conversation context
2. **Examine the code context**: Read the file at `path` around `line`
3. **Analyze the codebase**: Use Grep and Glob to understand related code and patterns
4. **Generate a thoughtful reply**: Address the reviewer's concern with specifics

When generating replies:
- Be concise but thorough
- Reference specific code when relevant
- Acknowledge valid points
- Suggest changes or improvements (but do NOT modify any files)
- If suggesting a fix, explain what should be changed and why

### Step 3: Post Replies

Post each reply using the helper script:

```bash
bash ${CLAUDE_PLUGIN_ROOT}/scripts/post-reply.sh --skill reply "<thread-id>" "<reply-body>"
```

Or for longer replies, write to a file first:

```bash
mkdir -p /tmp/github-devflow:reply/${REPO}/${PR_NUMBER}
# Write reply body to /tmp/github-devflow:reply/${REPO}/${PR_NUMBER}/reply.md
bash ${CLAUDE_PLUGIN_ROOT}/scripts/post-reply.sh --skill reply --file "<thread-id>" /tmp/github-devflow:reply/${REPO}/${PR_NUMBER}/reply.md
```

The script returns JSON with:
- `success`: Boolean indicating success
- `comment.id`: The created comment's ID
- `comment.url`: URL to the comment

### Step 4: Report Summary

After processing all threads, provide a summary:
- Number of threads processed
- Number of replies posted
- Any errors encountered

## Important Guidelines

### No Code Changes

**This skill must NOT modify any repository files.** Only suggest changes in replies:
- Do NOT use Edit tools
- Do NOT create or modify any repository files
- Only read files for context and analysis
- Suggest code changes in the reply text, not by editing files
- The Write tool is permitted ONLY for creating temp files under `/tmp/github-devflow:reply/` for the reply posting process

### Reply Quality

- Address the specific concern raised in the comment
- Provide context from the codebase when relevant
- Be professional and collaborative
- Keep replies focused and actionable

### Codebase Analysis

- Read the file mentioned in the thread's `path` field
- Look at surrounding code for context
- Check for related patterns elsewhere in the codebase
- Consider the reviewer's perspective

### Error Handling

- If `gh` CLI is not authenticated, inform the user to run `gh auth login`
- If the PR number is invalid, report the error clearly
- If no actionable threads are found, report that no replies are needed
- If posting a reply fails, report the error and continue with remaining threads

## Script Reference

### fetch-review-threads.sh

```
Usage: fetch-review-threads.sh <pr-number> [--filter-resolved] [--filter-skill <name>]

Options:
  --filter-resolved    Filter out resolved threads
  --filter-skill <name>  Filter out threads where the latest
                         comment contains the specified skill's signature
                         (github-devflow:<name>)

Output: JSON with repository info and thread array
```

### post-reply.sh

```
Usage: post-reply.sh [--skill <name>] <thread-id> <body>
       post-reply.sh [--skill <name>] --file <thread-id> <body-file>

Options:
  --skill <name>  Include skill identifier in signature
                  (e.g., --skill reply → "github-devflow:reply")

Arguments:
  thread-id   The GraphQL ID of the review thread (e.g., PRRT_xxx)
  body        The reply message text
  body-file   Path to a file containing the reply message

Note: Automatically appends a "Claude Code" signature to identify
      AI-generated replies for filtering in subsequent runs.

Output: JSON with success status and comment details
```

Versions

RepositoryScoreLicence
This page · hhiroshell/gh-devflow-plugins84MIT
lexfrei/ccc100BSD-3-Clause
rarexlabs/p11-public100MIT
rarexlabs/p11-public100MIT

Database snapshot: 13.11.2026 · package version 1be7f5f0da10 (SHA-256 digest of the entire package)

Downloads in the last 30 days: 0 · ranking

Report a problem with this skill: harmful content, incorrect descriptions or an author’s removal request.

Similar skills

  • 100review-pr-comments
    Address review comments on a GitHub pull request — fetch unresolved comments, investigate each issue, fix valid ones, reply, and resolve threads. Use this skill when the user asks to review PR comments, address PR feedback, handle PR review, respond to reviewer comments, or fix…
  • 90respond-to-review
    Work through the review comments on the user's own Bitbucket or GitHub pull request using the OmniDev tools - fix what needs fixing, draft replies, and resolve threads once the user approves. Use when the user asks to address review comments, reply to reviewers, or clear open…
  • 90comments
    Draft, refine, or respond to pull-request review comments. Use when a user asks to "write a review comment", "address review feedback", or "reply to a reviewer".
  • 100pr-comment-resolving
    Find and address all unresolved GitHub PR review comments on the current branch's pull request. Use when the user asks to resolve, address, respond to, or reply to PR review feedback — whether from humans, CodeRabbit, Copilot, Claude Code reviewer, or any other source. Triggers…
  • 84fix
    This skill should be used when the user asks to "fix PR comments", "fix review feedback", "fix PR #123", "address review comments", "resolve PR feedback", "apply review suggestions", "handle PR feedback", or wants to automatically process unresolved review threads on a pull…
  • 100answer-pr-reviews
    Use when the user asks to answer, address, or reply to review comments on one or more GitHub pull requests — "answer the review on #12", "address the comments on my PRs", "reply to the review findings" — in Claude Code, Codex, or any other agent. Not for reviewing a pull…

Feedback and reports

Your message goes to Bartosz Sokoliński. An email address is needed only for a reply. See the privacy policy.