address-review

Triage GitHub pull request review comments into a structured action plan.

413|31|Updated Mar 16, 2025
One-click install
npx skills add https://github.com/gittower/git-flow-next --skill address-review-gittower
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: address-review
Source: https://github.com/gittower/git-flow-next/tree/main/.claude/skills/address-review
Command: npx skills add https://github.com/gittower/git-flow-next --skill address-review-gittower

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill helps you process pull request review feedback without losing track of what to accept, dismiss, or partially implement. It creates an audit trail, keeps review responses organized, and supports a careful, confirmation-based workflow before any public GitHub actions happen.

Core Features & Use Cases

  • Review Triage: Fetches PR details, review comments, and inline discussion threads so each piece of feedback can be assessed in context.
  • Decision Making: Evaluates comments against project philosophy and classifies them as accepted, dismissed, or partial with a severity level.
  • Implementation Workflow: Writes a plan artifact, optionally applies the changes locally, runs build and test verification, and prepares draft replies for GitHub.
  • Use Case: A maintainer receives a large review on a branch and uses this Skill to produce a structured plan, make only the agreed changes, and prepare the exact responses before posting.

Quick Start

Use the address-review skill to evaluate review feedback for PR 42 and generate the plan artifact.

Frequently Asked Questions about address-review

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

FAQPage Schema
How do I triage GitHub pull request review feedback?

Triage GitHub pull request review feedback by fetching PR details, review comments, and inline discussion threads to evaluate each piece of feedback in context. This process classifies comments as accepted, dismissed, or partial with a severity level.

What is the best way to organize PR feedback and prepare reply drafts?

Organize PR feedback by creating a plan artifact that documents an audit trail of acceptance decisions. The workflow prepares draft replies for GitHub and resolves threads only after local implementation and build verification are complete.

How do I implement code review changes locally before pushing to a branch?

Implement code review changes locally by checking out the PR branch, applying the accepted feedback, and running build and test verification. This confirmation-based workflow ensures changes are validated before any public GitHub actions occur.

Can I evaluate GitHub PR comments against my project philosophy before responding?

Yes, you can evaluate GitHub PR comments against your project philosophy. The review triage mechanism assesses each comment and classifies it as accepted, dismissed, or partial, ensuring feedback aligns with project standards before public replies.

Does this PR feedback workflow require checking out a separate branch?

Yes, the PR feedback workflow requires branch checkout to apply changes locally. This ensures that review feedback is implemented and tested in an isolated environment before coordinated GitHub commenting and thread resolution are executed.