github-review-follow-up

Inspect unresolved GitHub pull request review threads and implement requested fixes locally.

5.3k|976|Updated Aug 25, 2025
One-click install
npx skills add https://github.com/Devin-AXIS/iPolloWork --skill github-review-follow-up
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: github-review-follow-up
Source: https://github.com/Devin-AXIS/iPolloWork/tree/main/examples/plugin-packages/github/skills/github-review-follow-up
Command: npx skills add https://github.com/Devin-AXIS/iPolloWork --skill github-review-follow-up

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Pull request reviews often accumulate scattered inline comments and unresolved threads, making it hard to track which feedback still needs action and risking premature thread resolution or unrequested replies.

Core Features & Use Cases

  • Thread Triage: Fetches pull request details and review threads via the GitHub service, then classifies them as actionable, informational, outdated, or ambiguous.
  • Scoped Fix Implementation: Groups actionable feedback by file or behavior, presents a numbered scope, and applies local changes traceable to each review thread.
  • Write Safety Controls: Never posts comments or resolves threads without explicit user intent, and stops to clarify ambiguous PR targets.
  • Use Case: A reviewer leaves eight inline comments on your PR. Use this Skill to list the unresolved actionable items, confirm which ones to fix, apply the changes locally, and run the narrowest relevant tests before replying.

Quick Start

Ask the agent to review the unresolved feedback on pull request number 42 in the current repository and fix the actionable items.

Frequently Asked Questions about github-review-follow-up

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

FAQPage Schema
How do I address unresolved GitHub pull request review comments?

Fetch the PR's review threads, separate actionable items from informational or outdated ones, then implement each fix in the local checkout with changes traceable to its thread. Run the narrowest relevant tests before replying or resolving anything.

How to group pull request review feedback before fixing it?

Group actionable review threads by file or behavior and present them as a numbered, concise scope. This lets you confirm which items are in scope before editing and keeps each change traceable to its original comment.

Can this automatically resolve GitHub review threads?

No. It never calls resolve-review-thread or posts comments unless the user explicitly asks, and it never marks a thread resolved before the corresponding change or explanation is complete.

What happens when review comments conflict with each other?

When comments conflict or would regress behavior, the workflow explains the conflict before making any edits. If the PR or repository target is ambiguous, it stops and requests the missing information rather than guessing.

Does it work with any GitHub pull request?

It works with any PR where owner, repo, and PR number can be resolved from the request, a URL, or the current branch, and where the GitHub service pull-request-detail and review-threads actions are available.