resolve-reviews

Fetch GitHub PR review comments, apply code fixes, and reply or resolve threads via gh CLI.

Updated Jun 28, 2026
One-click install
npx skills add https://github.com/Cohey0727/CodingAgentTools --skill resolve-reviews-cohey0727
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: resolve-reviews
Source: https://github.com/Cohey0727/CodingAgentTools/tree/main/skills/resolve-reviews
Command: npx skills add https://github.com/Cohey0727/CodingAgentTools --skill resolve-reviews-cohey0727

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Handling pull request review feedback is repetitive: reading each comment, judging whether it is valid, editing code, committing, pushing, replying, and resolving threads. This Skill automates that entire loop while distinguishing AI reviewers from human reviewers so the right level of caution is applied. ## Core Features & Use Cases - Automated review triage: Fetches PR review comments with the GitHub CLI, filters out pending reviews, self-comments, and already-answered threads, then classifies each comment as a valid fix or a reply-only rejection. - Reviewer-aware workflow: Bot reviewers (Copilot, CodeRabbit) and self-authored reviews are handled autonomously and their threads resolved via GraphQL, while any human reviewer comment pauses the flow for user confirmation. - End-to-end execution: Applies suggestion blocks verbatim, commits and pushes fixes, posts replies in the review's language, and prints a summary of fixes, replies, and resolved threads. - Use Case: After opening a PR that received four Copilot comments and one human comment, run the skill to fix the two valid findings, reject the over-defensive suggestions with stated reasoning, and resolve only the bot threads. ## Quick Start Ask the agent to resolve the review comments on PR 42, for example by saying "resolve the review comments on pull request 42".

Frequently Asked Questions about resolve-reviews

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

FAQPage Schema
How do I automatically respond to GitHub PR review comments?▼

Use the gh CLI to fetch review comments via the pulls comments API, analyze each for validity, apply code fixes, then post replies with the pulls/{number}/comments/{id}/replies endpoint. This skill automates that full sequence including commit, push, and thread resolution.

How to resolve GitHub review threads with the API?▼

Resolving review threads requires the GraphQL API, not REST. Query the pull request's reviewThreads to get each thread's node ID, then run the resolveReviewThread mutation with that threadId. The REST API has no endpoint for resolving threads.

Does this handle Copilot and CodeRabbit review comments differently?▼

Yes. Bot reviewers (user.type "Bot") and self-authored reviews are processed autonomously and their threads resolved after replying. Comments from human reviewers pause the workflow for user confirmation and their threads are never resolved automatically.

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

The reply endpoint must include the pull request number: repos/{owner}/{repo}/pulls/{pull_number}/comments/{comment_id}/replies. Omitting the pull number from the URL path causes GitHub to return 404 even when the comment ID is valid.

When should review feedback be rejected instead of fixed?▼

Reject feedback when no concrete failure path exists in the current code, when it demands defensive code for impossible inputs, or when it only offers theoretical safety at the cost of readability. The reply should state the rejection reason explicitly.