resolve-pr-parallel_skill

This skill resolves all PR comments in parallel by spawning dedicated agents for each thread, accelerating review feedback resolution.

TypeScript

10.5k

GitHub Stars

1

Bundled Files

2 months ago

Catalog Refreshed

4 months ago

First Indexed

Readme & install

Copy the install command, review bundled files from the catalogue, and read any extended description pulled from the listing source.

Installation

Preview and clipboard use veilstrat where the catalogue uses aiagentskills.

npx veilstrat add skill everyinc/compound-engineering-plugin --skill resolve-pr-parallel

SKILL.md2.4 KB

Overview

This skill automates resolving all unresolved pull request review comments by spawning parallel agents for each thread. It detects the PR context, batches unresolved review threads, runs per-thread resolvers in parallel, commits fixes, and programmatically marks threads resolved. The goal is fast, repeatable handling of review feedback with verification after completion.

How this skill works

The skill fetches unresolved, non-outdated review threads for a given PR using a GraphQL query or GitHub CLI fallback. It groups items into a Todo list by type, then spawns a pr-comment-resolver agent for each thread and runs them in parallel. After applying fixes, it commits and pushes changes and calls a GraphQL mutation to mark each thread resolved, then re-fetches threads to verify completion.

When to use it

You need to address many PR review comments quickly across multiple files.
A PR has several independent review threads that can be fixed concurrently.
You want reproducible, programmatic resolution of review feedback.
Batch-fixing stylistic or test-related comments across a codebase.
Verifying that all review threads are resolved after changes.

Best practices

Run the get-pr-comments script first to list unresolved, non-outdated threads.
Group threads by type (code change, question, style, tests) to assign appropriate resolver logic.
Keep resolver tasks independent to avoid conflicts during parallel commits.
Use clear commit messages referencing the PR and specific review feedback.
Re-run verification and repeat if any thread remains unresolved.

Example use cases

A large PR with dozens of small style and test-change comments that can be fixed in parallel.
Multiple reviewers left independent suggestions across files; run per-thread agents to implement each suggestion concurrently.
Automated bulk resolution for CI-identified test updates requested during review.
Scripted run as part of a maintenance workflow to clear long-standing unresolved threads.

FAQ

The skill falls back to GitHub CLI queries (gh pr view and gh api) to retrieve review comments and threads.

How are threads marked resolved?

After changes are committed and pushed, the resolve-pr-thread script runs a GraphQL mutation to mark each thread resolved, then verification confirms an empty result list.