From agent-skills
Fetches, organizes, and addresses PR review comments from GitHub. Use when user asks to review PR comments, fix PR feedback, check what reviewers said, address review comments, or handle bot suggestions on a pull request. Triggers on "review PR", "fix comments", "PR feedback", "what did reviewers say", "address PR feedback", "check PR comments".
npx claudepluginhub oryanmoshe/agent-skills --plugin agent-skillsThis skill uses the workspace's default tool permissions.
Fetch PR review comments, separate bot suggestions from human feedback, present a summary, then let the user select which comments to address.
Verifies tests pass on completed feature branch, presents options to merge locally, create GitHub PR, keep as-is or discard; executes choice and cleans up worktree.
Guides root cause investigation for bugs, test failures, unexpected behavior, performance issues, and build failures before proposing fixes.
Writes implementation plans from specs for multi-step tasks, mapping files and breaking into TDD bite-sized steps before coding.
Fetch PR review comments, separate bot suggestions from human feedback, present a summary, then let the user select which comments to address.
git branch --show-currentgh pr list --head <branch> --json number,title,url --jq '.[0]'# Inline review comments (on specific code lines)
gh api repos/{owner}/{repo}/pulls/<PR_NUMBER>/comments
# General PR comments
gh api repos/{owner}/{repo}/issues/<PR_NUMBER>/comments
# Review summaries
gh api repos/{owner}/{repo}/pulls/<PR_NUMBER>/reviews
Key fields:
created_at — display as relative time ("2 hours ago")position — null means outdated (code changed since comment)in_reply_to_id — reply thread, group with parentpath — file the comment is on| Category | Detection | Priority |
|---|---|---|
| Bot | Username contains [bot], ends with bot, or is a known CI tool | Lower — automated suggestions |
| Human | All other usernames | Higher — requires response |
## PR #123: "Add authentication flow"
### Human Reviewers (2 comments) — HIGH PRIORITY
- @alice: 1 comment on src/auth.ts (2 days ago)
- @bob: 1 comment on src/utils.ts (5 hours ago) ⚠️ OUTDATED
### Bot Suggestions (5 comments)
- 3 style/formatting (1 day ago)
- 2 potential improvements (1 day ago) ⚠️ 1 OUTDATED
Mark comments as ⚠️ OUTDATED when position is null (code changed since the comment was posted).
Use AskUserQuestion with multiSelect: true:
Which comments do you want me to address?
[ ] @alice: "Consider adding error handling for timeout" (2 days ago)
[ ] @bob: "This function could be simplified" (5h ago) ⚠️ OUTDATED
[ ] bot: "Missing return type annotation" (3 similar, 1 day ago)
Group similar bot comments to reduce noise. Show relative timestamps. Mark outdated comments — the user may skip these.
Dumping all comments raw: Always summarize and group first.
Treating all comments equally: Human comments get priority display over bot suggestions.
Open-ended questions: Use checkbox selection, not "which ones do you want me to fix?"
Fixing without asking: Always let the user select which comments to address.