pr-review-response

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

1|Updated Jul 7, 2026
One-click install
npx skills add https://github.com/seiggy/maf-copilot-studio-demo --skill pr-review-response-seiggy
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: pr-review-response
Source: https://github.com/seiggy/maf-copilot-studio-demo/tree/main/.squad/templates/skills/pr-review-response
Command: npx skills add https://github.com/seiggy/maf-copilot-studio-demo --skill pr-review-response-seiggy

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 unless each thread gets an individual reply. This Skill makes resolutions traceable by posting specific replies on every review thread after fixes are committed and pushed. ## Core Features & Use Cases - Thread-by-thread replies: Reads review comments via the GitHub MCP tool or gh api, then posts an individual 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 commit messages that reference the PR number and individual comment IDs. - Use Case: After Copilot flags three issues on a PR, the agent fixes each one, commits with comment references, replies to all three threads with the fix details, and resolves the automated threads. ## Quick Start Ask the agent to read the review comments on your pull request, fix the flagged issues, and reply to each 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 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.

Should agents resolve human reviewer threads on pull requests?

No. Only resolve threads from automated reviewers like Copilot where the fix fully addresses the comment. Human reviewer threads should be left open so the reviewer can confirm the fix and resolve it themselves.

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

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

What should a reply to a review comment include?

Include the commit SHA and a brief description of what changed, such as the function or pattern used. If a suggestion was not applied, explain why instead of staying silent, and avoid vague replies like just 'Fixed'.