Resolve all unresolved PR review comments by spawning parallel agents for each thread.
Works with
AI-first code editor with Composer
Before installing skills in Cursor, ensure your development environment meets these requirements:
node --versionresolve-pr-parallelExecute the skills CLI command in your project's root directory to begin installation:
Fetches resolve-pr-parallel from everyinc/compound-engineering-plugin and configures it for Cursor.
The CLI shows a list of agents. Use arrow keys and space to select Cursor:
Confirm successful installation by checking the skill directory location:
Restart Cursor to activate resolve-pr-parallel. Access via /resolve-pr-parallel in your agent's command palette.
We perform automated surface-level scans (Gen AI Scanner, Socket, Snyk) during installation. These checks detect common vulnerabilities but do not guarantee complete security. Always review skill source code and verify the publisher's reputation before production use.
Skills execute code in your environment. Always review source, verify the publisher, and test in isolation before production.
Submit your Claude Code skill and start earning
Create detailed user stories, acceptance criteria, and feature specs
Example
Generate user stories for 'password reset feature' with acceptance criteria, edge cases, and test scenarios
Reduce spec writing time by 50%, ensure comprehensive coverage
Research competitors, compare features, identify gaps
Example
Analyze 5 competitor products, create feature comparison matrix, suggest differentiation opportunities
Complete competitive research in 2 hours instead of 2 days
Evaluate features using frameworks (RICE, ICE, Kano) and create prioritized backlogs
Example
Score 20 feature ideas using RICE framework, generate prioritized roadmap with rationale
0
total installs
0
this week
13.4K
GitHub stars
0
upvotes
Run in your terminal
0
installs
0
this week
13.4K
stars
Resolve all unresolved PR review comments by spawning parallel agents for each thread.
Detect git context from the current working directory:
Fetch unresolved review threads using the GraphQL script at scripts/get-pr-comments:
bash 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
Create a task list of all unresolved items grouped by type (e.g., TaskCreate in Claude Code, update_plan in Codex):
Spawn a compound-engineering:workflow:pr-comment-resolver agent for each unresolved item.
If there are 3 comments, spawn 3 agents — one per comment. Prefer running all agents in parallel; if the platform does not support parallel dispatch, run them sequentially.
Keep parent-context pressure bounded:
If the PR is large enough that even batched short returns are likely to get noisy, use a per-run scratch directory such as .context/compound-engineering/resolve-pr-parallel/<run-id>/:
bash scripts/resolve-pr-thread THREAD_ID
Re-fetch comments to confirm all threads are resolved:
bash scripts/get-pr-comments PR_NUMBER
Should return an empty array []. If threads remain, repeat from step 1.
If a scratch directory was used and the user did not ask to inspect it, clean it up after verification succeeds.
Make data-driven prioritization decisions faster
Draft PRDs, status updates, and stakeholder presentations
Example
Create executive summary of Q3 roadmap, monthly progress report, feature launch announcement
Save 3-5 hours/week on communication overhead
Prerequisites
Time Estimate
30-60 minutes to see productivity improvements
Steps
Common Pitfalls
✓ Do
✗ Don't
💡 Pro Tips
✓ Use when
Use for user story writing, competitive research, roadmap prioritization, stakeholder communication, and PRD drafting. Best for reducing repetitive documentation and research work.
✗ Avoid when
Avoid for strategic product vision (requires deep customer empathy), pricing decisions (needs market and financial expertise), or when face-to-face customer discovery is more valuable than speed.
mattpocock/skills
parcadei/continuous-claude-v3
cursor/plugins
ailabs-393/ai-labs-claude-skills
pproenca/dot-skills
mattpocock/skills
resolve-pr-parallel reduced setup friction for our internal harness; good balance of opinion and flexibility.
Keeps context tight: resolve-pr-parallel is the kind of skill you can hand to a new teammate without a long onboarding doc.
Solid pick for teams standardizing on skills: resolve-pr-parallel is focused, and the summary matches what you get after install.
I recommend resolve-pr-parallel for anyone iterating fast on agent tooling; clear intent and a small, reviewable surface area.
resolve-pr-parallel has been reliable in day-to-day use. Documentation quality is above average for community skills.
Useful defaults in resolve-pr-parallel — fewer surprises than typical one-off scripts, and it plays nicely with `npx skills` flows.
Solid pick for teams standardizing on skills: resolve-pr-parallel is focused, and the summary matches what you get after install.
resolve-pr-parallel is among the better-maintained entries we tried; worth keeping pinned for repeat workflows.
Keeps context tight: resolve-pr-parallel is the kind of skill you can hand to a new teammate without a long onboarding doc.
resolve-pr-parallel fits our agent workflows well — practical, well scoped, and easy to wire into existing repos.
showing 1-10 of 41