claude-engineering-plugin/plugins/compound-engineering/commands/resolve_pr_parallel.md at f0a49f5b1833550691483d562f2387a1f7d44143

Files

Kieran Klaassen 6c5b3e40db [2.9.0] Rename plugin to compound-engineering

BREAKING: Plugin renamed from compounding-engineering to compound-engineering.
Users will need to reinstall with the new name:

  claude /plugin install compound-engineering

Changes:
- Renamed plugin directory and all references
- Updated documentation counts (24 agents, 19 commands)
- Added julik-frontend-races-reviewer to docs

🤖 Generated with [Claude Code](https://claude.com/claude-code)

Co-Authored-By: Claude <noreply@anthropic.com>

2025-12-02 17:32:16 -08:00

1.2 KiB

Raw Blame History

name, description, argument-hint

name	description	argument-hint
resolve_pr_parallel	Resolve all PR comments using parallel processing	[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

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

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
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.

1.2 KiB Raw Blame History