pr-review-response

Replies to GitHub PR review comment threads after fixes using gh CLI and GraphQL.

Updated Jun 2, 2026
One-click install
npx skills add https://github.com/codebytes/btt --skill pr-review-response-codebytes
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: pr-review-response
Source: https://github.com/codebytes/btt/tree/main/.squad/templates/skills/pr-review-response
Command: npx skills add https://github.com/codebytes/btt --skill pr-review-response-codebytes

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? When an agent fixes code based on PR review feedback, reviewers cannot tell which comments were addressed because the fixes happen silently. This Skill ensures every review thread gets an individual, traceable reply linking the comment to the actual fix. ## Core Features & Use Cases - Thread-by-thread replies: Reads review comments via the GitHub MCP tool or gh api, then posts a specific reply to each top-level comment referencing the commit SHA and what changed. - Optional thread resolution: Resolves agent-to-agent threads (e.g., Copilot reviews) via the GitHub GraphQL API while leaving human reviewer threads open for confirmation. - Traceable commit messages: Formats commits that reference the PR number and individual comment IDs for full feedback-to-fix traceability. - Use Case: After Copilot flags three issues on a pull request, the agent fixes each one, pushes a commit referencing all three comment IDs, replies individually to each thread explaining the change, and resolves the automated threads. ## Quick Start Ask the agent to read the review comments on your pull request, fix each issue, and reply to every review thread explaining what was changed.

Frequently Asked Questions about pr-review-response

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I reply to a GitHub PR review comment with gh CLI?

Use gh api repos/{owner}/{repo}/pulls/{pr_number}/comments/{comment_id}/replies with a -f body parameter. The comment_id must be the top-level comment in the thread, since the REST API cannot reply to replies.

How do I resolve a pull request review thread on GitHub?

Thread resolution is only available through the GitHub GraphQL API using the resolveReviewThread mutation. First query reviewThreads to get the thread node ID, matching it to comments via databaseId, then call the mutation with that threadId.

Should agents resolve review threads from human reviewers?

No. Threads from human reviewers should be left open so the reviewer can confirm the fix and resolve it themselves. Only agent-to-agent threads, such as Copilot review comments addressed by an agent, are safe to resolve.

Why does replying to a review comment return a 404 error?

The REST replies endpoint only accepts the ID of a top-level review comment. Attempting to reply to a comment that is itself a reply fails with a 404, so always use the original comment ID in the thread.

What should a reply to a review comment include?

A reply should reference the commit SHA and briefly describe what was changed, so the reviewer does not need to re-read the diff. When rejecting a suggestion, explain the technical reason instead of staying silent.