the-rabak/resolve-pr-parallel
plugins/compound-engineering/skills/resolve-pr-parallel/SKILL.md
Resolve all PR comments using parallel processing. Use when addressing PR review feedback, resolving review threads, or batch-fixing PR comments.
$ install --global
skillsauthnpx skillsauth add the-rabak/compound-engineering-plugin resolve-pr-parallelInstall this skill globally with one command. Works with Claude Code, Cursor, and Windsurf.
Security Scan Results
3 of 9 scanners reported clean
Some scanners were skipped, did not run, or reported a non-clean status. Review each row below.
3
Scanners Passed
9
Scanners in report
Clean
TrivyContainer and dependency vulnerability scanner
95%
Clean
SemgrepStatic code analysis for vulnerabilities
95%
Clean
mcp-scan (Snyk)Model Context Protocol security validation
95%
Skipped
Snyk (dep)Open source security scanning
50%
Skipped
Socket.devSupply chain security analysis
50%
Skipped
VirusTotalMulti-engine malware detection
50%
Skipped
CrowdStrikeAdvanced threat intelligence
50%
Skipped
OSV-ScannerOpen Source Vulnerability database check
50%
Skipped
OWASP Dep-Check
50%
Last scanned: Jul 15, 2026, 6:09 AM137.0s3 files scanned
SKILL.md
- name:
- resolve-pr-parallel
- description:
- Resolve all PR comments using parallel processing. Use when addressing PR review feedback, resolving review threads, or batch-fixing PR comments.
- model:
- claude-sonnet-5
- disable-model-invocation:
- true
Resolve 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
Gather unresolved review comments. Use one of these methods:
Option A: User pastes comments Ask the user to paste the PR/MR review comments. This is the most reliable method and works with any Git platform.
Option B: GitHub CLI (gh)
bash ${CLAUDE_PLUGIN_ROOT}/skills/resolve-pr-parallel/scripts/get-pr-comments PR_NUMBER [OWNER/REPO]
Option C: GitLab CLI (glab)
glab mr view MR_NUMBER --comments
Option D: Platform API (if access token is available)
For GitHub:
gh api repos/OWNER/REPO/pulls/PR_NUMBER/reviews
gh api repos/OWNER/REPO/pulls/PR_NUMBER/comments
For GitLab:
curl --header "PRIVATE-TOKEN: $GITLAB_TOKEN" \
"https://YOUR_GITLAB_HOST/api/v4/projects/PROJECT_ID/merge_requests/MR_IID/discussions"
For Bitbucket:
curl -u "$BITBUCKET_USER:$BITBUCKET_TOKEN" \
"https://api.bitbucket.org/2.0/repositories/WORKSPACE/REPO/pullrequests/PR_ID/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.
Before dispatching pr-comment-resolver, apply the shared Named Agent Dispatch protocol from commands/workflows/references/orchestration-protocol.md. Verify the agent metadata/source, resolve the concrete subagent identifier, and pass only the comment-specific payload. Do not read or paste the full agent body into the prompt.
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 (GitHub):
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 (GitHub)
- scripts/resolve-pr-thread - GraphQL mutation to resolve a thread by ID (GitHub)
Success Criteria
- All unresolved review threads addressed
- Changes committed and pushed
- Threads resolved (marked as resolved on the Git platform)
- Empty result from get-pr-comments on verify
Related Skills
the-rabak/html-artifact-mutator
development
VerifiedTrustedCommunity
Mutates a single field or content region of an existing self-contained HTML artifact in place (island-first, no-added-facts, injection-safe) without regenerating the document from scratch. Invoked by a workflow command whenever it needs to back-write into an artifact it already composed -- e.g. a ref/status update, or a content rewrite that must re-project the affected view -- never by the user directly.
1SKILL.mdUpdated Jul 15, 2026
the-rabak/html-artifact-composer
development
VerifiedTrustedCommunity
Composes a self-contained, interactive HTML artifact (island-first, single file, token-layer themed, injection-safe) from a workflow command's structured plan payload. Invoked by a workflow command at its artifact-write step -- currently `/workflows:plan` -- never by the user directly.
1SKILL.mdUpdated Jul 15, 2026
the-rabak/html-artifact-mutator
development
VerifiedTrustedCommunity
Mutates a single field or content region of an existing self-contained HTML artifact in place (island-first, no-added-facts, injection-safe) without regenerating the document from scratch. Invoked by a workflow command whenever it needs to back-write into an artifact it already composed -- e.g. a ref/status update, or a content rewrite that must re-project the affected view -- never by the user directly.
1SKILL.mdUpdated Jul 15, 2026
the-rabak/html-artifact-composer
development
VerifiedTrustedCommunity
Composes a self-contained, interactive HTML artifact (island-first, single file, token-layer themed, injection-safe) from a workflow command's structured plan payload. Invoked by a workflow command at its artifact-write step -- currently `/workflows:plan` -- never by the user directly.
1SKILL.mdUpdated Jul 15, 2026