Back to list
Zate

pr-feedback

by Zate

4🍴 0📅 Jan 24, 2026

SKILL.md


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 seeAlso:

  • skill: git-workflows when: git operations and PR strategy
  • 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:

FieldPurpose
reviewDecisionAPPROVED, CHANGES_REQUESTED, REVIEW_REQUIRED
reviewsList of reviews with state and body
commentsConversation comments

Parsing Feedback

Categorize feedback:

TypeDescription
BlockerMust fix before merge
SuggestionShould consider
QuestionNeeds response
NitpickNice 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:

  1. Make the fix
  2. Mark task complete in plan
  3. Reply to the comment on GitHub
  4. 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:

  1. Fetching current PR comments
  2. Parsing actionable items
  3. Presenting to user for selection
  4. Adding selected items to plan
  5. Updating Progress Log

Best Practices

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

Score

Total Score

60/100

Based on repository quality metrics

SKILL.md

SKILL.mdファイルが含まれている

+20
LICENSE

ライセンスが設定されている

+10
説明文

100文字以上の説明がある

0/10
人気

GitHub Stars 100以上

0/15
最近の活動

3ヶ月以内に更新がある

0/10
フォーク

10回以上フォークされている

0/5
Issue管理

オープンIssueが50未満

+5
言語

プログラミング言語が設定されている

+5
タグ

1つ以上のタグが設定されている

0/5

Reviews

💬

Reviews coming soon