home / skills / ratacat / claude-skills / resolve_pr_parallel

resolve_pr_parallel skill

/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_parallel

Review the files below or copy the command above to add this skill to your agents.

Files (1)
SKILL.md
1.2 KB
---
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.

Overview

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.

How this skill works

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.

When to use it

  • You have many independent PR review comments that can be addressed in parallel.
  • You want to speed up PR iteration and reduce manual context switching.
  • A PR contains multiple small fixes or clarifications across different files.
  • You prefer automated agents to propose and apply fixes before final review.

Best practices

  • Ensure your branch is up-to-date and all local changes are committed before running the skill.
  • Review the Todo list grouping to confirm items are safe to resolve in parallel.
  • Use small, focused pr-comment-resolver agents for isolated comments to avoid merge conflicts.
  • Run the final verification step (get-pr-comments) and re-run the workflow for any remaining threads.
  • Push and open CI checks after commits so reviewers can validate automated changes.

Example use cases

  • A feature branch receives 10 typo and documentation comments spread across files; run the skill to resolve them concurrently.
  • Multiple reviewers flag small logic tweaks in separate modules; agents implement and commit fixes in parallel.
  • Automate routine style and linter fixes requested in a review to clear noise from substantive feedback.
  • Quickly attempt a first-pass resolution of review threads before requesting another round of human review.

FAQ

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.