Skip to content

address-pr-feedback

Unified PR feedback workflow - collect, triage, and fix review comments in a single command.

Synopsis

/address-pr-feedback [pr-number | pr-url | branch] [--afk]

/rp1-dev-address-pr-feedback [pr-number | pr-url | branch] [--afk]

Description

The address-pr-feedback command handles PR review comments end-to-end: collecting feedback from GitHub, triaging by priority, fixing issues systematically, and reporting what was resolved.

The command executes four phases:

  1. Collection: Gathers and classifies review comments from GitHub
  2. Triage: Displays priority breakdown for review
  3. Fix: Addresses comments systematically in priority order
  4. Report: Generates resolution summary

Parameters

Parameter Type Required Description
pr-number number No PR number to process
pr-url string No GitHub PR URL
branch string No Branch name (auto-detects PR)
--afk flag No Run autonomously without prompts

If no parameter is provided, the command auto-detects the PR from the current branch.

Output

The command produces:

  • Feedback document: .rp1/work/pr-reviews/{identifier}-feedback-{NNN}.md
  • Resolution report: Displayed at completion

Examples

Basic Usage

Process feedback for the current branch's PR:

/address-pr-feedback

Specific PR

Target a specific PR by number:

/address-pr-feedback 42

Autonomous Mode

Run without prompts (useful for automation):

/address-pr-feedback 42 --afk

PR URL

Use a full GitHub URL:

/address-pr-feedback https://github.com/owner/repo/pull/42

Workflow Phases

Phase 1: Collection

Uses the pr-feedback-collector agent to:

  • Fetch PR review comments via gh CLI
  • Classify by priority (blocking, important, suggestion, style)
  • Extract actionable tasks
  • Generate structured feedback document

Phase 2: Triage

Displays summary for review:

## Feedback Triage

**PR**: #42 - Feature title
**Comments**: 8

### Priority Breakdown
- 🚨 Blocking: 1
- ⚠️ Important: 2
- 💡 Suggestions: 3
- 🎨 Style: 2

In interactive mode, you can review before proceeding. In --afk mode, auto-proceeds to fix phase.

Phase 3: Fix (Worktree Isolated)

All fix work is done in an isolated git worktree to allow review before merging:

  1. Creates an isolated worktree on the PR branch
  2. Processes comments in priority order (blocking -> important -> suggestions -> style)
  3. Commits each fix with conventional commit format
  4. Runs quality checks (lint, typecheck, tests)

For each comment:

  • Analyzes the concern and decides whether to implement or decline
  • Implements code changes if proceeding
  • Commits with fix(feedback): description
  • Updates feedback document with resolution status
  • Runs tests to verify

Important: Changes are NOT pushed automatically. The worktree is left intact for your review.

Phase 4: Report

Generates a consolidated summary:

## PR Feedback Resolution Summary

**PR**: #42 - Feature title
**Branch**: feature/my-feature

### Resolution Summary
- Blocking: 1/1
- Important: 2/2
- Suggestions: 3/3
- Style: 2/2

### Commits Made
5 commit(s) in worktree:
- abc1234 - fix(feedback): move JWT secret to env var
- def5678 - fix(feedback): add token expiration check

## Review Your Changes

The fixes have been made in an isolated worktree. **Changes are NOT pushed yet.**

**Worktree Location**:
path/to/worktree

**To review the changes**:
cd path/to/worktree
git log --oneline -10
git diff HEAD~5

**To push** (after review):
cd path/to/worktree
git push origin feature/my-feature

## Cleanup (Required)

When done reviewing, return to the main repo and remove the worktree:
git worktree remove path/to/worktree

See Also