resolve-pr-parallel

Automate unresolved PR review thread resolution with parallel agents.

Updated Mar 22, 2026
One-click install
npx skills add https://github.com/drhazemibclc/plate --skill resolve-pr-parallel-drhazemibclc
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: resolve-pr-parallel
Source: https://github.com/drhazemibclc/plate/tree/main/.codex/skills/resolve-pr-parallel
Command: npx skills add https://github.com/drhazemibclc/plate --skill resolve-pr-parallel-drhazemibclc

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill requires gh, jq, and includes scripts (resource) components.

What problem does it solve?

Resolve unresolved PR review threads by spawning parallel agents for each thread.

Core Features & Use Cases

  • Parallel resolution: spawn a resolver agent per unresolved thread to address feedback simultaneously.
  • Fallback and verification: if the GraphQL fetch fails, fall back to gh commands; verify threads are resolved at the end.
  • Context-aware: reads PR context, file paths, and comments to produce targeted resolutions.

Quick Start

Run the get-pr-comments script for your PR number and run the parallel resolver to address all unresolved threads.

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 multiple unresolved PR review threads in parallel?

Automating parallel resolution of unresolved PR review threads involves spawning a dedicated resolver agent for each thread to address feedback simultaneously. The process reads PR context, file paths, and comments to produce targeted resolutions.

Do I need GitHub CLI and jq installed to automate pull request code review resolution?

Yes, automating pull request code review resolution requires GitHub CLI and jq as dependencies. The process uses gh commands and GraphQL-based scripts to fetch, plan, execute, and verify thread resolutions, with fallback methods if the GraphQL fetch fails.

What is the best way to handle unresolved comments across multiple pull request threads?

The best way to handle unresolved comments across multiple pull request threads is parallel task orchestration. This method fetches thread data, applies targeted resolutions based on file paths and line numbers, and verifies that all threads are resolved at the end.

How do I fetch unresolved PR comments and context before running a parallel resolver?

To fetch unresolved PR comments and context before running a parallel resolver, run the get-pr-comments script for your PR number. This retrieves the necessary file paths, line numbers, and comments across multiple threads to plan the execution.

What happens if the GraphQL fetch fails during automated PR thread resolution?

If the GraphQL fetch fails during automated PR thread resolution, the system falls back to standard gh commands. This ensures the orchestration can still fetch context and execute thread resolutions before verifying the final results.