/pr-review — Address PR Comments | pds | ClaudePluginHub

Skill

/pr-review — Address PR Comments

From pds

Fetches GitHub PR review comments via gh CLI, inventories by file/line/author, addresses each with code fixes, runs tests, commits referencing PR, pushes, and reports resolutions.

$

npx claudepluginhub rmzi/portable-dev-system --plugin pds

Tool Access

This skill uses the workspace's default tool permissions.

Preview

Fetch PR review comments via `gh`, address each one with code fixes, run tests, commit, and push. Systematic process to ensure no comment is missed.

Supporting Assets

SKILL.md

Similar Skills

pr-comments-address

14

Reads open GitHub PR review comments, triages by severity and type, applies code fixes, and drafts replies. Use for addressing review feedback.

7 tools

ravn-ai-toolkit

address-github-comments

36.4k

Addresses review or issue comments on open GitHub Pull Requests using gh CLI: inspects threads, applies code fixes, and responds as resolved.

antigravity-awesome-skills

skill-lookup

159.9k

Searches, retrieves, and installs Agent Skills from prompts.chat registry using MCP tools like search_skills and get_skill. Activates for finding skills, browsing catalogs, or extending Claude.

Stats

Stars19

Forks0

Last CommitMar 31, 2026

Actions

View Source View Plugin View on GitHub View README

Tags

review-comments

Help us improve

Share bugs, ideas, or general feedback.

/pr-review — Address PR Comments

Fetch PR review comments via gh, address each one with code fixes, run tests, commit, and push. Systematic process to ensure no comment is missed.

When to Use

After receiving review feedback on a pull request
When a PR has unresolved comments that need code changes
When iterating on a PR after reviewer suggestions

Protocol

1. Fetch Comments

# Get PR number from current branch
PR_NUMBER=$(gh pr view --json number -q '.number')
REPO=$(gh repo view --json nameWithOwner -q '.nameWithOwner')

# Fetch all review comments (inline code comments)
gh api repos/$REPO/pulls/${PR_NUMBER}/comments --paginate

# Also fetch general PR comments (top-level discussion)
gh api repos/$REPO/issues/${PR_NUMBER}/comments --paginate

# Check for requested changes
gh pr view $PR_NUMBER --json reviews -q '.reviews[] | select(.state == "CHANGES_REQUESTED") | .body'

2. Inventory Comments

List every comment with:

File and line — where the comment applies
Author — who made the comment
Content — what they said
Status — resolved/unresolved

Group comments by file for efficient addressing.

3. Address Each Comment

For each unresolved comment:

Read the relevant code context
Understand the reviewer's concern
Implement the fix or improvement
If you disagree with the suggestion, explain why in a reply rather than silently ignoring it

4. Test

Run the project's test suite to confirm changes don't break anything:

# Run tests (project-specific command)
npm test    # or equivalent

5. Commit

Commit with a message that references the PR:

git commit -m "fix: address PR review feedback (#<PR_NUMBER>)

- <summary of change 1>
- <summary of change 2>"

6. Push

git push

7. Report

Summarize what was addressed:

## PR Review Response
### Addressed
- `file.ts:42` — [reviewer]: [concern] -> [what you changed]
- `other.ts:15` — [reviewer]: [concern] -> [what you changed]
### Discussed (not changed)
- `file.ts:88` — [reviewer]: [concern] -> [why no change needed]
### Remaining
- [any comments that need further discussion]

Rules

Address every comment. Do not skip or ignore review comments.
Commit atomically. Group related fixes into logical commits, not one giant commit.
Test before pushing. Never push untested changes.
Explain disagreements. If you disagree with a suggestion, reply with reasoning.

See Also

/pds:verify — Self-check before pushing
/pds:finish — Branch completion protocol