resolve-pr-parallel
npx machina-cli add skill everyinc/compound-engineering-plugin/resolve-pr-parallel --openclawResolve PR Comments in Parallel
Resolve all unresolved PR review comments by spawning parallel agents for each thread.
Context Detection
Claude Code automatically detects git context:
- Current branch and associated PR
- All PR comments and review threads
- Works with any PR by specifying the number
Workflow
1. Analyze
Fetch unresolved review threads using the GraphQL script:
bash ${CLAUDE_PLUGIN_ROOT}/skills/resolve-pr-parallel/scripts/get-pr-comments PR_NUMBER
This returns only unresolved, non-outdated threads with file paths, line numbers, and comment bodies.
If the script fails, fall back to:
gh pr view PR_NUMBER --json reviews,comments
gh api repos/{owner}/{repo}/pulls/PR_NUMBER/comments
2. Plan
Create a TodoWrite list of all unresolved items grouped by type:
- Code changes requested
- Questions to answer
- Style/convention fixes
- Test additions needed
3. Implement (PARALLEL)
Spawn a pr-comment-resolver agent for each unresolved item in parallel.
If there are 3 comments, spawn 3 agents:
- Task pr-comment-resolver(comment1)
- Task pr-comment-resolver(comment2)
- Task pr-comment-resolver(comment3)
Always run all in parallel subagents/Tasks for each Todo item.
4. Commit & Resolve
- Commit changes with a clear message referencing the PR feedback
- Resolve each thread programmatically:
bash ${CLAUDE_PLUGIN_ROOT}/skills/resolve-pr-parallel/scripts/resolve-pr-thread THREAD_ID
- Push to remote
5. Verify
Re-fetch comments to confirm all threads are resolved:
bash ${CLAUDE_PLUGIN_ROOT}/skills/resolve-pr-parallel/scripts/get-pr-comments PR_NUMBER
Should return an empty array []. If threads remain, repeat from step 1.
Scripts
- scripts/get-pr-comments - GraphQL query for unresolved review threads
- scripts/resolve-pr-thread - GraphQL mutation to resolve a thread by ID
Success Criteria
- All unresolved review threads addressed
- Changes committed and pushed
- Threads resolved via GraphQL (marked as resolved on GitHub)
- Empty result from get-pr-comments on verify
Source
git clone https://github.com/everyinc/compound-engineering-plugin/blob/main/plugins/compound-engineering/skills/resolve-pr-parallel/SKILL.mdView on GitHub Overview
This skill automatically resolves unresolved PR review threads by launching a dedicated agent for each thread and processing them in parallel. It accelerates feedback loops, helps batch-fix comments, and keeps PRs moving when there are multiple threads across code, questions, or style fixes.
How This Skill Works
Claude Code detects the current PR context, fetches unresolved, non-outdated threads, and groups them into a TodoWrite list by type. It then spawns a pr-comment-resolver agent for every item and runs all agents in parallel. After changes are committed and the threads are resolved via GraphQL, it re-fetches the threads to verify an empty result.
When to Use It
- Address PR review feedback across multiple threads in a single PR.
- Resolve review threads quickly by parallelizing per-thread work.
- Batch-fix code, questions, and style/convention comments together.
- When PR has several unresolved comments with file/line references.
- During PR maintenance to ensure all outstanding threads are cleared before a merge.
Quick Start
- Step 1: Analyze unresolved threads with the get-pr-comments script.
- Step 2: Plan and spawn pr-comment-resolver tasks for each thread, then run in parallel.
- Step 3: Commit changes, resolve threads via resolve-pr-thread, push, and verify with get-pr-comments.
Best Practices
- Always fetch unresolved threads first to confirm scope.
- Group items by type (code changes, questions, style, tests).
- Run all per-thread tasks in parallel and monitor for failures.
- Use clear commit messages that reference the PR feedback.
- Verify by re-fetching comments to ensure an empty result.
Example Use Cases
- PR #456: resolved 4 unresolved comments in parallel and pushed.
- Resolves code-change, question, and test-addition threads in one pass.
- Aggregates review threads from multiple files and resolves them concurrently.
- When a reviewer leaves several small follow-ups across files, resolve in parallel.
- Maintains PR momentum by eliminating backlog of unresolved threads quickly.
