Run any Skill in Manus with one click

resolve-pr-parallel

Stars8

Forks0

UpdatedFebruary 27, 2026 at 15:14

Resolve all PR comments using parallel processing. Use when addressing PR review feedback, resolving review threads, or batch-fixing PR comments.

Installation

Install with Codex or Claude Copy this prompt, paste it into Codex, Claude, or another assistant, and let it review the skill page and install it for you.

Run Skill in Manus

Source

aimi-so

aimi-so/aimi-engineering-plugin

View GitHub Repository View Creator Repositories

Download

Run Skill in Manus

Related occupationsSOC

Based on SOC occupation classification

Software Quality Assurance Analysts and TestersComputer and Mathematical Occupations·SOC 15-1253

File Explorer

3 files

SKILL.md

readonly

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.
argument-hint	[optional: PR number or current PR]
disable-model-invocation	true
allowed-tools	Bash(gh ), Bash(git ), Read

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

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

More from this repository

same repository

task-planner

aimi-so/aimi-engineering-plugin

Generate tasks.json directly from a feature description. Full pipeline: research, spec analysis, story decomposition, JSON output. Triggers on: plan feature, generate tasks, create task list, direct planning.

2026-07-038

aimi-learnings

aimi-so/aimi-engineering-plugin

Triage the pending friction queue captured by aimi hooks. Groups events by scope (project / plugin / inbox), presents top patterns for review, and drafts promotion proposals locally for human review. Never auto-commits, never opens PRs. Triggers on /aimi:learnings, "triage friction", "review friction events", "drain friction queue".

2026-06-098

story-executor

aimi-so/aimi-engineering-plugin

Execute a single story from the tasks file autonomously. This skill defines how Task-spawned agents execute individual stories. Used internally by /aimi:execute and /aimi:status commands.

2026-06-038

brainstorm

aimi-so/aimi-engineering-plugin

Guide collaborative brainstorming sessions to clarify requirements before planning. Covers batched multiple-choice questions, adaptive exit, and design document capture. Triggers on: brainstorm, explore idea, think through, what should we build.

2026-04-298

frontend-design

aimi-so/aimi-engineering-plugin

Use when the user wants to design, redesign, shape, critique, audit, polish, clarify, distill, harden, optimize, adapt, animate, colorize, extract, or otherwise improve a frontend interface. Covers websites, landing pages, dashboards, product UI, app shells, components, forms, settings, onboarding, and empty states. Handles UX review, visual hierarchy, information architecture, cognitive load, accessibility, performance, responsive behavior, theming, anti-patterns, typography, fonts, spacing, layout, alignment, color, motion, micro-interactions, UX copy, error states, edge cases, i18n, and reusable design systems or tokens. Also use for bland designs that need to become bolder or more delightful, loud designs that should become quieter, live browser iteration on UI elements, or ambitious visual effects that should feel technically extraordinary. Trigger keywords: design, UI, interface, frontend, visual, layout, typography, color, spacing, motion, responsive, component, theme, palette, animation, accessibility

2026-04-298

git-worktree

aimi-so/aimi-engineering-plugin

This skill manages Git worktrees for isolated parallel development. It handles creating, listing, switching, and cleaning up worktrees with a simple interactive interface, following KISS principles.

2026-04-148

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.
argument-hint	[optional: PR number or current PR]
disable-model-invocation	true
allowed-tools	Bash(gh ), Bash(git ), Read

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

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