resolve-pr-parallel

Resolves unresolved GitHub PR review threads by spawning parallel agents per comment.

Updated Jan 23, 2026
One-click install
npx skills add https://github.com/stephschofield/beth --skill resolve-pr-parallel-stephschofield
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: resolve-pr-parallel
Source: https://github.com/stephschofield/beth/tree/main/.github/skills/resolve-pr-parallel
Command: npx skills add https://github.com/stephschofield/beth --skill resolve-pr-parallel-stephschofield

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) components.

What problem does it solve? Addressing dozens of PR review comments one by one is slow and error-prone. This Skill fetches all unresolved review threads from a GitHub pull request and processes each comment in parallel, then marks threads as resolved via the GitHub GraphQL API. ## Core Features & Use Cases - Unresolved Thread Fetching: Uses a GraphQL script to retrieve only unresolved, non-outdated review threads with file paths, line numbers, and comment bodies. - Parallel Comment Resolution: Spawns one pr-comment-resolver agent per unresolved item so multiple review comments are fixed concurrently. - Programmatic Thread Resolution: Resolves each thread on GitHub via a GraphQL mutation and verifies completion by re-fetching until no threads remain. - Use Case: After a reviewer leaves 8 comments on your pull request, run this Skill to batch-fix all feedback, commit the changes, push, and mark every thread resolved in one workflow. ## Quick Start Ask the agent to resolve all unresolved review comments on the current pull request, optionally specifying a PR number.

Frequently Asked Questions about resolve-pr-parallel

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

FAQPage Schema
How do I resolve all PR review comments at once on GitHub?▼

Fetch unresolved review threads with the get-pr-comments script, spawn a parallel agent per comment to implement fixes, commit and push the changes, then resolve each thread with the resolve-pr-thread GraphQL mutation.

How to fetch unresolved GitHub PR review threads with GraphQL?▼

Run the get-pr-comments script with a PR number; it queries the GitHub GraphQL API for reviewThreads and filters to items where isResolved and isOutdated are both false, returning paths, lines, and comment bodies.

Does this work with any pull request or only the current branch?▼

It works with any PR by passing the PR number as an argument. If omitted, the GitHub CLI detects the repository from the current git context, and an OWNER/REPO argument can override detection.

What happens if the get-pr-comments script fails?▼

Fall back to standard GitHub CLI commands: gh pr view with the reviews and comments JSON fields, plus gh api for the pulls comments endpoint, to retrieve the review feedback manually.

How do I verify all PR threads are resolved?▼

Re-run the get-pr-comments script after committing and resolving. It should return an empty array; if any threads remain, repeat the analyze-plan-implement cycle until none are left.