pr-comment-responder

PR Comment Responder

Coordinates PR review responses through context gathering, comment tracking, and orchestrator delegation.

Triggers

Phrase	Action
respond to PR comments	Full workflow
address review feedback on PR #123	Full workflow
handle PR review comments	Full workflow
fix PR review issues	Full workflow
reply to reviewer on PR #123	Target specific PR

Quick Reference

Context Inference (Phase -1)

ALWAYS extract PR context from prompt first. Never prompt for information already provided.

Extract PR context from user prompt or use gh pr view to get PR metadata.

Supported patterns:

• Text: PR 806, PR #806, pull request 123, #806
• URLs: github.com/owner/repo/pull/123

See references/workflow.md Phase -1 for full details.

Tools

Operation	Command
Context extraction	Extract PR number from prompt or use gh pr view
PR metadata	gh pr view [number] --json title,body,state,author,baseRefName,headRefName
Comments	gh pr view [number] --json comments,reviewDecision,reviews
Reviewers	gh pr view [number] --json reviewRequests,reviews
Reply	gh pr comment [number] --body "[response]"
Reaction	gh api repos/{owner}/{repo}/issues/comments/{id}/reactions -f content=eyes
Resolve thread	gh api graphql with resolveReviewThread mutation

Reviewer Priority

Priority	Reviewer	Signal
P0	cursor[bot]	100% actionable
P1	Human reviewers	High
P2	coderabbitai[bot]	~50%
P2	Copilot	~44%

Domain-Based Priority

Comments are classified into domains for priority-based triage:

Priority	Domain	Keywords	Use Case
P0	Security	CWE-*, vulnerability, injection, XSS, SQL, CSRF, auth, secrets, credentials, TOCTOU, symlink, traversal	Process FIRST - security-critical issues
P1	Bug	error, crash, exception, fail, null, undefined, race condition, deadlock, memory leak	Address functional issues
P2	Style	formatting, naming, indentation, whitespace, convention, prefer, consider, suggest	Apply improvements when time permits
P3	Summary	Bot-generated summaries (## Summary, ### Overview)	Informational only

Domain-First Processing Workflow:

# Get all review comments and PR comments
comments=$(gh api repos/{owner}/{repo}/pulls/{number}/comments)
issue_comments=$(gh api repos/{owner}/{repo}/issues/{number}/comments)

# Process by domain priority:
# 1. Security (CWE, vulnerabilities, injection) - process FIRST
# 2. Bug (errors, crashes, null references)
# 3. Style (formatting, naming, conventions)
# 4. General comments
# 5. Skip summary comments (bot-generated noise)

Benefits:

• Security issues processed before style suggestions
• Reduces noise from bot-generated summaries
• Enables metrics tracking (security vs style comment distribution)

When to Use

Use this skill when:

• A PR has unaddressed review comments from humans or bots
• You need to systematically triage and respond to all review feedback
• CI review bots (CodeRabbit, Copilot, cursor) left comments requiring action

Use direct gh pr comment instead when:

• Replying to a single known comment (no triage needed)
• You already know the exact response to post

Process

Phase 1: Context and Gather

1. Extract PR number from prompt (BLOCKING) or use gh pr view
2. Search Brain memory for pr-comment-responder related notes
3. Gather PR metadata, reviewers, all comments (use --group-by-domain for priority triage)
4. Batch eyes reactions on all comments

Phase 2: Triage and Delegate

1. Generate comment map (track in session or Brain memory note)
2. Delegate each comment to orchestrator (process security domain first)
3. Implement changes via orchestrator delegation

Phase 3: Verify

1. All comments resolved (COMPLETE or WONTFIX)
2. No new comments after 45s wait
3. CI checks passing, all threads resolved, commits pushed

See references/workflow.md for full phase details.

Verification

• [ ] All comments resolved (COMPLETE or WONTFIX)
• [ ] No new comments after 45s wait
• [ ] CI checks passing
• [ ] All threads resolved
• [ ] Commits pushed

See references/gates.md for gate implementation.

Response Templates

See references/templates.md for:

• Won't Fix responses
• Clarification requests
• Resolution replies

Bot Handling

See references/bots.md for:

• Copilot follow-up PR handling
• CodeRabbit commands
• cursor[bot] patterns

Anti-Patterns

Avoid	Why	Instead
Replying to bot summaries as actionable comments	Wastes time on informational noise	Skip Summary domain comments
Processing style before security	Misses critical issues	Process domains in P0-P3 priority order
Prompting user for PR number already in prompt	Redundant and frustrating	Parse PR number from input text or use gh pr view

Extension Points

• Add new domain classifiers for comment triage
• Add reviewer priority entries for new bot integrations
• Add response templates in references/templates.md