forge-address-pr-feedback

Identify and resolve unresolved GitHub pull request feedback threads.

65|5|Updated Feb 6, 2026
One-click install
npx skills add https://github.com/mgratzer/forge --skill forge-address-pr-feedback
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: forge-address-pr-feedback
Source: https://github.com/mgratzer/forge/tree/main/skills/forge-address-pr-feedback
Command: npx skills add https://github.com/mgratzer/forge --skill forge-address-pr-feedback

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Analyze and address unresolved feedback on a GitHub pull request to ensure feedback is addressed systematically and efficiently.

Core Features & Use Cases

  • Identify unresolved PR threads using GraphQL and investigate the context of each comment.
  • Apply targeted code changes, run lint/format checks, and commit with clear messages.
  • Reply to each unresolved thread individually with precise, actionable, and traceable responses.
  • Optional: create follow-up issues for out-of-scope feedback to keep PRs focused.

Quick Start

Address unresolved PR feedback by reading threads, applying changes, and replying to each thread individually.

Frequently Asked Questions about forge-address-pr-feedback

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

FAQPage Schema
How do I resolve unresolved GitHub PR feedback systematically?

Resolve unresolved GitHub PR feedback by identifying review threads via GraphQL, applying targeted code changes, and replying to each thread individually. This systematic approach ensures every comment is addressed with clear commit messages and actionable responses.

Can I automate replying to individual code review threads on GitHub?

Yes, you can automate replying to individual code review threads. The process fetches unresolved threads using GraphQL, applies the requested code modifications, and posts precise, traceable responses directly to each specific thread.

What is the best way to process unresolved PR review comments thread-by-thread?

Processing unresolved PR review comments thread-by-thread involves investigating the context of each comment, applying targeted code changes, running lint checks, and committing with clear messages before posting individual replies.

Do I need GraphQL to fetch GitHub pull request threads for automated code review?

Yes, GraphQL is required to fetch unresolved GitHub pull request threads. It queries the review threads so you can read target files, apply changes, and generate per-thread replies systematically.

How do I handle out-of-scope feedback when addressing GitHub pull request reviews?

Handle out-of-scope feedback by creating follow-up issues for those comments. This optional step keeps your GitHub pull requests focused while ensuring the feedback is tracked and addressed later.

Why address PR feedback individually instead of batch committing changes?

Addressing PR feedback individually provides precise, traceable responses to each thread. Batch committing obscures which changes resolve which comments, whereas thread-by-thread replies keep the review process transparent and systematic.