resolve-pr-parallel

Resolve unresolved PR review threads in parallel using GraphQL and gh api.

50|14|Updated Mar 11, 2026
One-click install
npx skills add https://github.com/All-The-Vibes/ATV-StarterKit --skill resolve-pr-parallel-all-the-vibes
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: resolve-pr-parallel
Source: https://github.com/All-The-Vibes/ATV-StarterKit/tree/main/.github/skills/resolve-pr-parallel
Command: npx skills add https://github.com/All-The-Vibes/ATV-StarterKit --skill resolve-pr-parallel-all-the-vibes

SYSTEM DOCUMENTATION & REQUIREMENTS

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

What problem does it solve?

This skill automates the painful and error-prone task of closing out unresolved PR review threads by orchestrating parallel reviewers, speeding up feedback resolution and ensuring nothing slips through the cracks.

Core Features & Use Cases

  • Automated parallel resolution: Spawns a dedicated resolver per unresolved thread to accelerate feedback processing.
  • Fallback and resilience: Uses GraphQL to fetch threads and falls back to gh api when GraphQL is unavailable.
  • End-to-end workflow: From fetch to commit and push, to verification of thread status across multiple PRs.

Quick Start

Provide a PR number to automatically resolve all unresolved review threads in parallel.

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?

You can resolve unresolved PR threads in parallel by spawning a dedicated resolver for each thread, fetching them via a GraphQL query and executing per-thread tasks concurrently to accelerate feedback processing across any PR number.

What's the best way to automate closing unresolved GitHub pull request comments?

Automating unresolved GitHub pull request comments is best handled by spawning parallel resolvers for each thread, executing end-to-end workflow steps from fetch to push, and verifying thread status to ensure nothing slips through the cracks.

Do I need gh CLI and jq to resolve PR review threads automatically?

Yes, you need gh CLI and jq installed to resolve PR review threads automatically. The skill requires gh to execute API requests and jq to parse the GraphQL JSON responses before spawning parallel resolvers.

What happens if GraphQL is unavailable when fetching PR threads?

If GraphQL is unavailable when fetching PR threads, the skill falls back to using the gh api to retrieve unresolved review threads, ensuring resilience and allowing the parallel resolution process to continue functioning.

Can I use this parallel resolver across multiple PR numbers?

Yes, you can use this parallel resolver across multiple PR numbers. It applies to any PR number and orchestrates end-to-end workflows from fetching threads to committing, pushing, and verifying thread status across them.