resolve-pr-comments

Resolve GitHub PR review threads by fixing, declining, or escalating each comment.

7|12|Updated Mar 26, 2026
One-click install
npx skills add https://github.com/OpenRouterTeam/docs --skill resolve-pr-comments-openrouterteam
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: resolve-pr-comments
Source: https://github.com/OpenRouterTeam/docs/tree/main/.agents/skills/resolve-pr-comments
Command: npx skills add https://github.com/OpenRouterTeam/docs --skill resolve-pr-comments-openrouterteam

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? After a code review, a PR can accumulate dozens of unresolved review threads that require tedious manual follow-through: fixing code, replying to reviewers, resolving threads, and keeping an audit trail. This Skill drives every unresolved thread to a verdict — fixed, declined, or escalated to a human — so review feedback actually turns into merged code. ## Core Features & Use Cases - Thread triage and resolution: Fetches unresolved review threads via the GitHub GraphQL API, sorts each into fix, decline, or escalate buckets, then replies and resolves with an auditable trail. - Resolution log maintenance: Keeps a running resolution table in the PR description so reviewers and humans can verify every verdict without opening each thread. - Stacked-PR and CI awareness: Handles restacks, wrong-layer comments, flaky CI signals, and permission-limited environments like Cursor cloud agents. - Use Case: After running a deep code-quality review on a pull request, invoke this Skill to work through all 40 resulting threads — pushing batched fixes, replying with commit SHAs, and escalating only the two naming decisions that need a human. ## Quick Start Resolve all the open review comments on my current pull request, fixing what you can and escalating anything that needs my decision.

Frequently Asked Questions about resolve-pr-comments

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

FAQPage Schema
How do I resolve all review comments on a GitHub pull request?▼

Fetch unresolved review threads with the GitHub GraphQL API, triage each into fix, decline, or escalate, then reply to the thread's last comment and call the resolveReviewThread mutation. Push fixes in batches so replies can cite real commit SHAs.

How to reply to and resolve a GitHub review thread with gh CLI?▼

Post a reply with gh api POST to repos/{owner}/{repo}/pulls/<PR>/comments/<databaseId>/replies, then run the GraphQL resolveReviewThread mutation with the thread ID. Reply first so reviewers have a verdict to verify before the thread closes.

When should a PR review comment be escalated instead of fixed?▼

Escalate when a fix contradicts explicit instructions, two reviewers conflict, the decision is product or naming related, the fix would expand the PR's scope, or a low-severity nit needs substantial new code. Reply tagging the human and leave the thread unresolved.

Why does the GitHub resolve thread mutation return a 403 error?▼

A 403 means the token lacks write permissions on the repository, which is common on cloud agents with read-only gh tokens. In that case post replies through the agent's PR tool and state in the reply that the thread could not be resolved.

What is the difference between resolving PR comments and babysitting a PR?▼

Resolving PR comments finishes a review that already happened by driving existing threads to zero in the current session. Babysitting hands the PR to a separate session that procures review and drives it to approval, pushing its own commits to the branch.