pr-review-response

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

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

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 pull request number 42, fix the flagged issues, and reply to each review thread with 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 containing your reply text. The comment_id must be the top-level comment in the thread, since the REST API cannot reply to replies.

How to resolve a GitHub review thread programmatically?

Thread resolution is only available through the GitHub GraphQL API using the resolveReviewThread mutation with the thread's node ID. First query reviewThreads to map thread IDs to comment databaseIds, then run the mutation for each thread you want to resolve.

Should agents resolve human reviewer threads on pull requests?

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

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

The GitHub REST API only supports replying to top-level review comments, not to replies within a thread. If you pass the ID of a nested reply, the endpoint returns a 404, so always use the original comment's ID.

What should a reply to a PR 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.