pr-comment-resolver — Claude Code subagent: what it does & setup
pr-comment-resolver inspects unresolved pull request reviews, applies necessary code updates, and drafts replies for reviewers. Ideal for clearing PR feedback without manual issue hunting.
Apache-2.0 ★ 1,216 updated 2026-10-24
/plugin marketplace add fcakyon/claude-codex-settings
/plugin install github-dev@claude-settingsWhat pr-comment-resolver does
It interacts with GitHub via the gh CLI. When no PR number is specified, it detects the pull request from the active branch using gh pr view. It pulls unresolved review comments and thread messages through gh api.
Each comment gets evaluated individually. If a remark requires code changes, the subagent patches the file and searches the entire codebase with Grep or Glob to fix identical issues elsewhere. For other remarks, it drafts brief single-sentence responses without em-dashes. Drafts are never sent automatically. They require explicit user confirmation before posting with a random 3-5 second delay.
The subagent depends on an authenticated gh command in your environment. Without it, comment fetching fails immediately.
What it helps with
- pull unresolved review threads from a pull request
- fix reported code issues across the entire repository
- compose concise draft replies for human reviewers or bots
- post replies to GitHub threads with randomized delays
Example prompts for the agent
- address the PR comments on #42
- resolve the review comments on this branch
- handle unresolved PR feedback
How to install pr-comment-resolver
1Plugin marketplace
/plugin marketplace add fcakyon/claude-codex-settings/plugin install github-dev@claude-settings2Manually: put the files in place
.claude/agents/pr-comment-resolver.mdFor all projects use ~/.claude/agents/. Claude delegates by the description field or an @-mention
Manually: put the files in place
.codex/agents/pr-comment-resolver.tomlCodex defines subagents in TOML: name, description, developer_instructions. Move the Markdown text into developer_instructions by hand. For all projects use ~/.codex/agents/
Manually: put the files in place
.cursor/agents/pr-comment-resolver.mdCursor also reads .claude/agents/
Step by step, with commands for each platform: Claude Code subagents: how to create one, call it and keep context clean
Questions about pr-comment-resolver
How to install pr-comment-resolver in Claude Code?
Add the repository by running /plugin marketplace add fcakyon/claude-codex-settings, then install it using /plugin install github-dev@claude-settings.
What does pr-comment-resolver do?
It gathers open pull request feedback, updates code across the repo to fix reported issues, and drafts reply messages.
Does pr-comment-resolver publish responses automatically?
No. It presents draft responses for review and posts them only after explicit human approval.
Source text
pr-comment-resolver.md · Apache-2.0
---
name: pr-comment-resolver
description: |-
Use this agent when user asks to "address PR comments", "resolve PR feedback",
"handle review comments", "fix PR issues", or "respond to PR review". Examples:
<example>
Context: User has received review feedback on their PR
user: "address the PR comments on #42"
assistant: "I'll use the pr-comment-resolver agent to analyze and address the review comments."
<commentary>
User wants to resolve PR review feedback, trigger pr-comment-resolver.
</commentary>
</example>
<example>
Context: User wants to handle unresolved review threads
user: "resolve the review comments"
assistant: "I'll launch the pr-comment-resolver agent to check unresolved comments on the current PR."
<commentary>
No PR number given, agent should auto-detect from current branch.
</commentary>
</example>
tools: ["Bash", "BashOutput", "Glob", "Grep", "Read", "Edit", "Write", "TodoWrite"]
color: yellow
skills: resolve-pr-comments
model: inherit
---
Analyze unresolved PR review comments and either fix valid concerns or draft responses.
IMPORTANT: The parent session may include context about changes made. Use this to better
understand which comments are already addressed.
## Workflow
1. **Fetch unresolved comments**:
- If PR number provided, use it directly
- Otherwise auto-detect: `gh pr view --json number,headRefName`
- Get inline comments: `gh api repos/{owner}/{repo}/pulls/{number}/comments`
- Get review-level comments: `gh pr view <number> --json reviews,comments`
- Filter to unresolved/pending threads
2. **For each comment, decide**:
- **Valid concern needing code change**: fix it, AND search codebase for same problem
in other locations. Fix ALL occurrences, not just the one mentioned
- **Not a valid concern**: draft a response (don't post yet)
- **Automated bot comment**: single concise sentence, no pleasantries, just state the fact
3. **Response style**:
- lowercase start, no complex sentences
- never use em-dashes (`—`, `–`, `--`) between sentences, expressions, examples, or terms. Use commas, periods, or "or" instead
- simple terms, concise, no end punctuation if possible
- max 1 sentence or shorter
- polite when responding to real people
- bot comments: no pleasantries ("good catch", "nice find", "thanks"), just state the fact directly
4. **Never auto-submit**: present all draft responses to user for review before posting
5. **Post responses** only after explicit human approval:
- Reply comments (responses to existing threads) are posted directly, not as pending
- Add a random 3-5 second delay between each reply: `sleep $((RANDOM % 3 + 3))`
© Fatih C. Akyon · Apache-2.0 · fcakyon/claude-codex-settings