home / skills / ratacat / claude-skills / resolve_pr_parallel
This skill resolves all PR comments in parallel by spawning dedicated agents for each item and updating threads.
npx playbooks add skill ratacat/claude-skills --skill resolve_pr_parallelReview the files below or copy the command above to add this skill to your agents.
---
name: resolve_pr_parallel
description: Resolve all PR comments using parallel processing
---
## Arguments
[optional: PR number or current PR]
Resolve all PR comments using parallel processing.
Claude Code automatically detects and understands your git context:
- Current branch detection
- Associated PR context
- All PR comments and review threads
- Can work with any PR by specifying the PR number, or ask it.
## Workflow
### 1. Analyze
Get all unresolved comments for PR
```bash
gh pr status
bin/get-pr-comments PR_NUMBER
```
### 2. Plan
Create a TodoWrite list of all unresolved items grouped by type.
### 3. Implement (PARALLEL)
Spawn a pr-comment-resolver agent for each unresolved item in parallel.
So if there are 3 comments, it will spawn 3 pr-comment-resolver agents in parallel. liek this
1. Task pr-comment-resolver(comment1)
2. Task pr-comment-resolver(comment2)
3. Task pr-comment-resolver(comment3)
Always run all in parallel subagents/Tasks for each Todo item.
### 4. Commit & Resolve
- Commit changes
- Run bin/resolve-pr-thread THREAD_ID_1
- Push to remote
Last, check bin/get-pr-comments PR_NUMBER again to see if all comments are resolved. They should be, if not, repeat the process from 1.
This skill automates resolving all pull request (PR) comments by creating and running parallel comment-resolver agents. It detects the current git/PR context, gathers unresolved review threads, and executes independent subagents to implement fixes and resolve threads. The goal is fast, reliable bulk resolution of PR feedback with minimal manual coordination.
The skill inspects the git context to find the current branch and associated PR or accepts an explicit PR number. It collects all unresolved comments and groups them into a Todo list by type. For each unresolved item it spawns a pr-comment-resolver agent and runs all agents in parallel, commits changes, and resolves review threads by invoking the provided helper scripts.
How does the skill know which PR to operate on?
It automatically detects the current branch and its associated PR or accepts an explicit PR number passed as an argument.
What happens if parallel edits conflict?
Conflicts may occur; follow the workflow to inspect failures, resolve conflicts manually, and rerun the process for remaining threads.