skills.rest
LumaKernel
LumaKernelCOMMUNITY
Explore all skills by this author →
𝕏@lumc_GitHub

reply-pr-review

Investigate and reply to unresolved GitHub pull request review comments using gh CLI.

17|1|Updated Dec 29, 2019
Search Tags:#code review#pull request#github#GraphQL#gh cli#reply#review comments
One-click install
npx skills add https://github.com/LumaKernel/dotfiles --skill reply-pr-review-lumakernel
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: reply-pr-review
Source: https://github.com/LumaKernel/dotfiles/tree/main/common/claude/skills/reply-pr-review
Command: npx skills add https://github.com/LumaKernel/dotfiles --skill reply-pr-review-lumakernel

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Handling unresolved PR review comments requires manually fetching threads, verifying each claim against the actual code, and writing evidence-based replies, which is repetitive and error-prone. ## Core Features & Use Cases - Unresolved Thread Retrieval: Fetches unresolved review threads via the GitHub GraphQL API using gh api graphql, avoiding the broken gh pr view path. - Fact-Checked Replies: Investigates each comment against the actual code and specifications before replying, supporting agreement with fixes, evidence-based rebuttals, or neutral trade-off analysis. - Use Case: After pushing changes to a PR, run this Skill to pull all unresolved review threads, verify each reviewer's claim against the diff, and post sourced replies with documentation links to every thread. ## Quick Start Reply to all unresolved review comments on the current pull request after verifying each point against the code.

Frequently Asked Questions about reply-pr-review

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

FAQPage Schema
How do I reply to unresolved PR review comments with gh CLI?▼

Fetch unresolved review threads with `gh api graphql` querying reviewThreads where isResolved is false, then reply to each thread via the API. Pass the GraphQL query from a file with `-F query=@file` to avoid bash history expansion issues with `!`.

How to list unresolved review threads on a GitHub pull request?▼

Use the GitHub GraphQL API through `gh api graphql` to query pullRequest.reviewThreads and filter nodes where isResolved is false. The REST-based `gh pr view` is unreliable due to Projects Classic deprecation.

Why does gh pr view fail when checking pull requests?▼

The `gh pr view` command is affected by the GitHub Projects Classic deprecation and may not work in some contexts. Use `gh pr diff` for changes and `gh api graphql` for review thread data instead.

Should I always apply reviewer suggestions to my PR?▼

No. Verify each comment against the actual code and specifications first. Fix and explain correct points, rebut incorrect ones with evidence and documentation links, and present trade-offs neutrally when judgment is split.

Why does my GraphQL query break in bash with exclamation marks?▼

Bash history expansion interprets `!` in inline strings, corrupting GraphQL queries containing `String!` type markers. Write the query to a temporary file and pass it with `gh api graphql -F query=@/tmp/query.graphql`.

Related Skills

Explore More Software Engineering Skills→
cxm6467cxm6467

gh-copilot-review

Automate GitHub Copilot review workflows by applying suggestions and resolving threads.

Community
Advanced
ai-heroai-hero
5

ship-pr

Trigger auto-approve on a GitHub PR, merge on approval, and verify post-merge deployment health.

Official
Advanced
Open-PawsOpen-Paws
3

code-review

Automate layered code review for pull requests in CI pipelines.

Official
Advanced
ulises-jeremiasulises-jeremias
2

gh-address-comments

Automate processing and responding to GitHub pull request comments via gh CLI.

Community
Basic