resolve-review-comments

Automate GitHub PR review workflows by reading threads, applying approved changes, and pushing updates.

4|2|Updated Feb 25, 2026
One-click install
npx skills add https://github.com/LaiTszKin/apollo-toolkit --skill resolve-review-comments
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: resolve-review-comments
Source: https://github.com/LaiTszKin/apollo-toolkit/tree/main/resolve-review-comments
Command: npx skills add https://github.com/LaiTszKin/apollo-toolkit --skill resolve-review-comments

SYSTEM DOCUMENTATION & REQUIREMENTS

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

What problem does it solve?

Read GitHub pull request review comments, analyze each thread, decide whether to adopt feedback, implement adopted changes, push updates to the same PR branch, and resolve addressed review threads. Use when users ask to process PR review feedback by PR number or current branch context.

Core Features & Use Cases

  • Identify unresolved threads and decide on per-thread adoption based on content and code context.
  • Implement only adopted feedback, run tests if present, push commits to the PR branch, and resolve addressed threads.
  • Maintain visibility of unresolved or rejected feedback for follow-up.

Quick Start

Provide the PR number or ensure the current branch of the repository is the target PR context.

Frequently Asked Questions about resolve-review-comments

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

FAQPage Schema
How do I automate resolving GitHub pull request review comments?

To automate resolving GitHub pull request review comments, this skill reads PR threads, decides on per-thread adoption, applies approved changes, and pushes updates to the PR branch to resolve addressed feedback.

Do I need the gh CLI installed to automate PR review workflows?

Yes, you need the gh CLI installed and authenticated to automate PR review workflows, as the skill relies on it to read review threads and push updates to your writable git repository.

What happens to unresolved or rejected review threads when applying PR feedback?

When applying PR feedback, unresolved or rejected review threads remain intact and visible for follow-up, ensuring only adopted feedback is implemented and addressed threads are resolved.

Can I process pull request review feedback using a branch context instead of a PR number?

Yes, you can process pull request review feedback using the current branch context of your repository, allowing the skill to identify the target PR and analyze threads without requiring an explicit PR number.

How does automating code review adoption handle code changes and testing?

Automating code review adoption involves implementing minimal scoped code changes based on approved feedback, running tests if present, and pushing commits to the PR branch to update the review status.

What is the best way to apply approved GitHub PR feedback while leaving unresolved threads untouched?

The best way to apply approved GitHub PR feedback is using an automated workflow that evaluates each thread, applies only adopted changes, and leaves unresolved threads untouched for manual follow-up.