pr-review-address

name	pr-review-address
description	Use when addressing GitHub PR review feedback; gather all comments and requested changes, classify them, fix valid feedback, push back with evidence when appropriate, and reply to every thread.
version	1.0.0
author	Eric Hansen + Hermes Agent
license	MIT
metadata	{"hermes":{"tags":["github","pull-requests","code-review","feedback"],"related_skills":["github-code-review","github-pr-workflow","gh-body-safe"]}}

Address PR Review Feedback

Overview

Handle PR feedback deliberately. Do not blindly accept every suggestion, and do not ignore comments. Gather all feedback, classify it, fix valid issues, and respond to every reviewer point with evidence.

When to Use

Use when the user says:

• address PR comments
• handle review feedback
• fix requested changes
• update the PR based on review

Workflow

1. Identify the PR.
2. Check GitHub auth if any command fails:

   gh auth status
   

3. Gather all feedback:

   gh pr view <number> --comments
   gh api repos/:owner/:repo/pulls/<number>/reviews
   gh api repos/:owner/:repo/pulls/<number>/comments
   

4. Classify each item:
   • Blocking bug/security/correctness issue
   • Valid improvement
   • Style/preference
   • Question
   • Disagree / counterproductive
   • Out of scope
5. Make focused code changes for valid feedback.
6. Run relevant tests/linters.
7. Reply to every comment. Use gh-body-safe patterns for multi-line replies.
8. Push only when explicitly requested or already authorized for this PR-update flow.

Reply Style

For fixed items:

Fixed in <commit/branch>. I changed X because Y and verified with Z.

For disagreements:

I don't think we should make this change because <specific reason>. The existing behavior is needed for <case>, and I verified <evidence>.

For out-of-scope items:

Good suggestion, but this is outside the scope of this PR. I recommend tracking it separately because <reason>.

Verification Checklist

• All review comments and threads were gathered.
• Each item was classified.
• Valid issues were fixed with focused changes.
• Tests/linters relevant to the change were run.
• Every comment received a reply or resolution.
• Any disagreement includes evidence, not vibes.