pr-resolve

Resolve unresolved GitHub pull request review threads by applying fixes, replying, and marking them resolved.

Updated Apr 16, 2026
One-click install
npx skills add https://github.com/real-case/marvin-toolkit --skill pr-resolve-real-case
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: pr-resolve
Source: https://github.com/real-case/marvin-toolkit/tree/main/plugins/marvin/skills/pr-resolve
Command: npx skills add https://github.com/real-case/marvin-toolkit --skill pr-resolve-real-case

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Addressing pull request review feedback is tedious and error-prone: you must find every unresolved thread, decide what each comment actually asks for, apply minimal fixes, push, and then reply to and resolve each thread so reviewers see closure. This Skill automates that entire loop using the GitHub CLI and GraphQL API. ## Core Features & Use Cases - Unresolved thread discovery: Queries the GitHub GraphQL API to fetch only unresolved review threads, including outdated threads re-anchored to current code. - Grounded classification and planning: Re-reads the cited code before classifying each thread as requested-change, question, suggestion, spec-conflict, or unfounded, then presents a plan with draft replies for approval. - All-or-nothing fixes with closure: Applies minimal edits, commits and pushes, then replies to each thread and resolves it, verifying closure by re-querying. - Use Case: A reviewer left eight comments on your PR. Run the skill to fetch the unresolved threads, approve the proposed fix plan, and let it apply the changes, push a commit, reply to each thread with the fix SHA, and mark them resolved. ## Quick Start Ask the assistant to resolve the review comments on pull request 42 and approve the proposed change plan when presented.

Frequently Asked Questions about pr-resolve

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 via the GitHub GraphQL API, classify each comment against the actual code, apply minimal fixes, push a commit, then reply to each thread and mark it resolved. This skill automates that full loop with an approval checkpoint before any code changes.

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

Use gh api graphql with the addPullRequestReviewThreadReply mutation to post a reply keyed on the thread's node id, then call the resolveReviewThread mutation with the same id. Pass the reply body via -f or stdin, never -F, to avoid type coercion.

Can I fetch only unresolved review threads from GitHub?▼

Yes, but only through the GraphQL API, since the REST API cannot distinguish resolved from unresolved threads. Query reviewThreads on the pull request and filter nodes where isResolved is false.

What happens when a review comment conflicts with the project spec?▼

Comments that contradict the spec are classified as spec-conflict and change no code. The skill posts a reply asking the reviewer to confirm overriding the spec and leaves the thread open until the reviewer responds.

Why does the skill stop instead of applying partial review fixes?▼

Review comments on one PR are often interdependent, so a half-applied pass leaves the branch in an inconsistent state. If any comment cannot be grounded in the actual code, the all-or-nothing rule halts the pass and asks the user for clarification.