ce-resolve-pr-feedback

Evaluate and resolve GitHub PR feedback across multiple review threads.

2|Updated Apr 30, 2026
One-click install
npx skills add https://github.com/thisisryanswift/zellij-agent-tools --skill ce-resolve-pr-feedback
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: ce-resolve-pr-feedback
Source: https://github.com/thisisryanswift/zellij-agent-tools/tree/main/.opencode/skills/ce-resolve-pr-feedback
Command: npx skills add https://github.com/thisisryanswift/zellij-agent-tools --skill ce-resolve-pr-feedback

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill requires gh, jq, and includes scripts (resource) components.

What problem does it solve?

Resolve PR review feedback by evaluating validity and fixing issues in parallel. Use when addressing PR review comments, resolving review threads, or fixing code review feedback.

Core Features & Use Cases

  • Evaluate unresolved inline review threads and identify actionable feedback.
  • Spawn parallel agents to craft replies and apply fixes, then resolve threads.
  • Support targeted and full PR modes via PR numbers or URLs.

Quick Start

Supply a PR number or URL to begin automatically evaluating and resolving review feedback across threads.

Frequently Asked Questions about ce-resolve-pr-feedback

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I resolve GitHub PR review feedback in parallel?

Resolve GitHub PR review feedback in parallel by spawning multiple agents that evaluate unresolved inline threads, craft replies, apply fixes, and mark threads as resolved simultaneously.

Can I target a specific pull request number to fix code review comments?

Yes, you can target a specific pull request by supplying a PR number or URL, which restricts the automated feedback evaluation and thread resolution actions to that single pull request.

Do I need gh and jq installed to automate pull request thread resolution?

Yes, you need the gh and jq dependencies to fetch pull request data via GitHub APIs and parse JSON structures, enabling the script suite to analyze and resolve code review threads.

What is the best way to handle multiple unresolved code review threads on GitHub?

The best way to handle multiple unresolved code review threads is coordinating parallel agents that independently evaluate feedback validity, apply fixes, and resolve threads for a fast turnaround.

Does this automated PR feedback resolution work with full pull requests or only targeted threads?

This automated PR feedback resolution supports both targeted and full PR modes, allowing you to limit actions to specific threads or evaluate and resolve all unresolved feedback across the entire pull request.