replying-to-pr-review-threads

Reply to and resolve GitHub pull request review threads via GraphQL.

2|Updated Jun 1, 2017

Search Tags:#automation #code review #github #graphql #pull requests #gh cli #inline review threads

Ready to run

npx skills add https://github.com/carlos-algms/dotfiles --skill replying-to-pr-review-threads

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: replying-to-pr-review-threads
Source: https://github.com/carlos-algms/dotfiles/tree/main/AI-configs/skills/replying-to-pr-review-threads
Command: npx skills add https://github.com/carlos-algms/dotfiles --skill replying-to-pr-review-threads

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill helps you correctly read, reply to, and resolve GitHub pull request review threads—especially nested inline diff threads—when the needed APIs and identifiers (REST vs GraphQL IDs) don’t map cleanly in the CLI.

Core Features & Use Cases

Read all PR review surfaces: fetches both top-level review comments and inline diff review thread trees.
Reply to a specific review thread: posts replies to the correct thread using the REST comment ID while also handling the AI-reviewer context.
Resolve a thread reliably: looks up the GraphQL thread ID and resolves via GraphQL when REST has no resolve endpoint.
Use-case examples: when you see an anchor like pull/N#discussion_rNNN, want to respond to CodeRabbit/AI reviewer feedback, or need to cleanly resolve the exact inline thread you’re viewing from the CLI.

Quick Start

Use the replying-to-pr-review-threads skill to respond to a specific review anchor like pull/123#discussion_r456 and then resolve that exact inline thread from the CLI.

Frequently Asked Questions about replying-to-pr-review-threads

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

FAQPage Schema

How do I reply to a GitHub PR inline review thread from the CLI?▼

To reply to a GitHub PR inline review thread from the CLI, you post a response using the REST comment ID mapped from the discussion anchor. This skill uses gh api to handle the REST reply while maintaining the AI reviewer context.

Why does resolving a GitHub pull request review thread fail with standard gh CLI commands?▼

Resolving a GitHub pull request review thread fails because the REST API lacks a resolve endpoint. You must look up the GraphQL thread ID and resolve the inline review thread using a GraphQL mutation via gh api instead.

What is a discussion_rNNN anchor and how does it map to GitHub GraphQL reviewThreads?▼

A discussion_rNNN anchor is a REST comment ID from a GitHub PR review URL. To interact with nested inline threads via GraphQL, you must map this REST ID to the corresponding GraphQL reviewThreads nodes to locate the exact thread.

Can I read all pull request review comment surfaces including inline diff threads using gh api?▼

Yes, you can read all PR review surfaces using gh api by fetching both top-level review comments and inline diff review thread trees. This skill queries GraphQL to retrieve the nested inline thread structures that standard CLI commands miss.

What is the best way to resolve an inline CodeRabbit review thread from the terminal?▼

The best way to resolve an inline CodeRabbit review thread from the terminal is to map the discussion_rNNN REST ID to a GraphQL thread ID, post a reply via REST, and execute a GraphQL mutation to resolve the thread using gh api.