This Claude skill streamlines the post-review development process by automatically parsing Pull Request (PR) comments and integrating them into an actionable development plan. It helps developers efficiently categorize feedback, prioritize blockers, and track the resolution of reviewer concerns, ensuring a faster and more organized path to merging code.

When should I use pr-feedback?

pr-feedback is useful in the following scenarios: • Converting complex GitHub PR review threads into structured task lists within a development plan. • Categorizing reviewer feedback into blockers, suggestions, and nitpicks to prioritize critical fixes. • Tracking the progress of multiple review iterations to ensure every piece of feedback is addressed before the next push. • Automating the generation of status replies to reviewers by linking addressed tasks to specific commits.

name	pr-feedback
description	This skill should be used for integrating PR review comments back into devloop plan, parsing review feedback, addressing reviewer concerns
whenToUse	PR has review comments, feedback to address, review iterations, changes requested, responding to reviewers
whenNotToUse	No open PR, PR already merged, creating new PR
- skill	plan-management
when	updating plan with new tasks

PR Feedback Integration

Parse PR review comments and integrate actionable items into the devloop plan.

When to Use

PR has review comments or change requests
Reviewer requested changes
Need to track which feedback has been addressed
Iterating on PR after initial review

Fetching PR Feedback

Get PR details with comments:

# View PR with all comments
gh pr view --json number,title,body,comments,reviews,reviewDecision

# Get review comments (inline code comments)
gh api repos/{owner}/{repo}/pulls/{number}/comments

# Get PR conversation comments
gh api repos/{owner}/{repo}/issues/{number}/comments

Key fields to extract:

Field	Purpose
`reviewDecision`	APPROVED, CHANGES_REQUESTED, REVIEW_REQUIRED
`reviews`	List of reviews with state and body
`comments`	Conversation comments

Parsing Feedback

Categorize feedback:

Type	Description
Blocker	Must fix before merge
Suggestion	Should consider
Question	Needs response
Nitpick	Nice to have

Identify actionable items:

Look for patterns:

"Please..." / "Could you..." → Action request
"This should..." / "Consider..." → Suggestion
"Why..." / "What if..." → Question
"Nit:" / "Minor:" → Low priority

Adding to Plan

Create PR Feedback section in plan:

## PR Feedback

PR #123 - Review by @reviewer (CHANGES_REQUESTED)

### Blockers
- [ ] [PR-123-1] Fix null handling in parseConfig (@reviewer)
- [ ] [PR-123-2] Add tests for edge cases (@reviewer)

### Suggestions
- [ ] [PR-123-3] Consider caching config (@reviewer)

### Questions
- [ ] [PR-123-4] Respond: Why not use existing parser? (@reviewer)

Task ID format: [PR-{number}-{item}]

Tracking Resolution

When addressing feedback:

Make the fix
Mark task complete in plan
Reply to the comment on GitHub
Push changes

Reply template:

gh pr comment {number} --body "Addressed in commit {sha}:
- Fixed null handling
- Added edge case tests"

Example Workflow

# 1. Check PR status
gh pr view --json reviewDecision,reviews

# 2. If changes requested, get details
gh pr view --comments

# 3. Parse into plan tasks (manual or use /devloop:pr-feedback)

# 4. Work through feedback tasks

# 5. Push and reply
git push
gh pr comment --body "Ready for re-review"

Integration with /devloop:pr-feedback

The /devloop:pr-feedback command automates:

Fetching current PR comments
Parsing actionable items
Presenting to user for selection
Adding selected items to plan
Updating Progress Log

Best Practices

Address blockers first
Reply to each comment when resolved
Push frequently during feedback iteration
Re-request review when ready

pr-feedback

When & Why to Use This Skill

Use Cases