pr-review-respond

Manages Hub employee onboarding and exit workflows in a single place.

Updated May 1, 2026
One-click install
npx skills add https://github.com/arthur-debert/release --skill pr-review-respond-arthur-debert
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: pr-review-respond
Source: https://github.com/arthur-debert/release/tree/main/skills/pr-review-respond
Command: npx skills add https://github.com/arthur-debert/release --skill pr-review-respond-arthur-debert

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill requires gh, jq.

What problem does it solve?

This Skill helps you efficiently reply to and resolve GitHub pull request review comments so PRs don’t get stuck in an unreadable, perpetually unresolved state across review rounds.

Core Features & Use Cases

  • List Unresolved Review Threads: Fetches unresolved review threads via a GraphQL query and surfaces the exact thread IDs, file locations, and first comment IDs needed for follow-up actions.
  • Reply With Reliable Multi-line Markdown: Posts review replies to the correct comment using authenticated gh API calls with jq-built JSON payloads for safe handling of markdown, code blocks, and special characters.
  • Resolve Threads Programmatically: Resolves review threads using the correct GraphQL thread ID mutation so the “Unresolved” status clears after you address feedback.
  • Use Case: After Copilot or human reviewers comment on a PR, use this Skill to triage what to fix versus what to rationale-reply, then reply and resolve each thread after pushing fixups.

Quick Start

Use pr-review-respond to list unresolved review threads for PR 123, reply to each relevant thread using gh plus jq, and then resolve every addressed thread.

Frequently Asked Questions about pr-review-respond

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

FAQPage Schema
How do I resolve unresolved GitHub pull request review threads using the command line?

You can resolve GitHub pull request review threads by using the gh CLI to fetch unresolved threads via a GraphQL query and then executing a resolve thread mutation with the correct GraphQL thread ID to clear the unresolved status.

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

You reply to a GitHub PR review comment by using the gh api command to POST a reply to the correct REST databaseId. Using jq to construct the JSON payload ensures safe handling of markdown and special characters.

Do I need jq to automate pull request review thread resolution with gh?

Yes, jq is required to safely construct JSON payloads for authenticated gh REST and GraphQL API calls. It ensures reliable handling of multi-line markdown and code blocks when posting replies to review threads.

What is the difference between GraphQL thread IDs and REST databaseIds for GitHub PR reviews?

GraphQL thread IDs are required to resolve a review thread mutation, while REST databaseIds are needed to reply to a specific review comment. Correctly separating these two IDs ensures your gh API calls successfully update the thread.

Can I automate post-review triage for Copilot feedback on GitHub PRs?

Yes, you can automate post-review triage for Copilot or human feedback by listing unresolved threads, posting replies, and resolving them programmatically. This is useful in CI agents or cloud sessions where standard scripts are unavailable.