resolve_pr_parallel

Resolve GitHub pull request review comments by dispatching parallel agents and committing changes.

Updated Aug 23, 2026
One-click install
npx skills add https://github.com/adamfeldman/compound-workflows --skill resolve-pr-parallel-adamfeldman
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: resolve_pr_parallel
Source: https://github.com/adamfeldman/compound-workflows/tree/main/plugins/compound-workflows/skills/resolve-pr-parallel
Command: npx skills add https://github.com/adamfeldman/compound-workflows --skill resolve-pr-parallel-adamfeldman

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) components.

What problem does it solve?

This Skill automates the resolution of GitHub Pull Request review comments by processing them in parallel, significantly speeding up the code review feedback loop.

Core Features & Use Cases

  • Parallel Agent Dispatch: Spawns individual agents for each unresolved comment thread, allowing simultaneous processing.
  • Automated Git Integration: Detects current branch, associated PR, and comments automatically. Works with specified PR numbers.
  • Disk-based Output: Agents write detailed resolution reports to disk, preventing context exhaustion and allowing for later review.
  • Use Case: When a PR has multiple review comments across different files, this skill will assign each comment to a separate agent, process them concurrently, and then commit the changes and resolve the threads.

Quick Start

Use the resolve_pr_parallel skill to resolve all comments on the current PR.

Frequently Asked Questions about resolve_pr_parallel

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

FAQPage Schema
How do I automatically resolve GitHub pull request review comments in parallel?

To resolve GitHub pull request review comments in parallel, this skill dispatches a dedicated background agent for each unresolved thread, implements the necessary code changes concurrently, commits them, and programmatically resolves the threads via the GitHub API.

How does parallel processing work when addressing PR review feedback?

Parallel processing of PR review feedback works by spawning individual agents for each unresolved comment thread, allowing simultaneous code changes across different files, which significantly speeds up the code review feedback loop.

Can I use this to fix code review comments across multiple files simultaneously?

Yes, you can use this to fix code review comments across multiple files simultaneously. It assigns each comment to a separate agent, processes them concurrently, commits the changes, and resolves the threads automatically.

Do I need to specify a PR number to resolve review threads automatically?

You do not strictly need to specify a PR number to resolve review threads automatically. The skill can detect the current Git branch and its associated pull request, but it also supports working with a specified PR number if provided.

What happens to the resolution reports after the pull request comments are resolved?

After pull request comments are resolved, the agents write detailed resolution reports to disk. This disk-based output prevents context exhaustion and allows you to review the automated changes and progress later.

Why does resolving PR comments in parallel prevent context exhaustion?

Resolving PR comments in parallel prevents context exhaustion because the dispatched agents persist their resolution reports to disk rather than keeping all thread data and code changes in active memory.