Pr Comment Resolver
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: 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." User wants to resolve PR review feedback, trigger…
- Type
- Subagent
- Repository
- fcakyon/claude-codex-settings
- GitHub stars
- 1.2k
- License
- Apache-2.0
- Repo last updated
- Sep 24, 2026
- Source file
- plugins/github-dev/agents/pr-comment-resolver.md
- Model
- inherit
What Pr Comment Resolver is
Pr Comment Resolver is a subagent published in the fcakyon/claude-codex-settings repository on GitHub, which has about 1.2k stars. The repository describes itself as: “Battle-tested Claude Code, OpenAI Codex, Cursor configs, plugins, hooks and agents with Kimi, MiniMax and GLM API support.”
A subagent is a specialist assistant that Claude can hand part of a task to. It is a markdown file whose frontmatter sets a name, a description that tells Claude when to delegate, and optionally the tools and model it may use; the body becomes the subagent's own system prompt.
Because a subagent works in its own context, it keeps the main conversation focused: Claude can send a narrow job, such as a review or a specialised analysis, to Pr Comment Resolver and get back a compact result.
It is set up to use these tools: Bash, BashOutput, Glob, Grep, Read, Edit, Write, TodoWrite. Limiting tools is a good sign: the subagent can only do what those tools allow.
How to install Pr Comment Resolver
Claude Code
- Download pr-comment-resolver.md from the repository.
- Save it to ~/.claude/agents/ to use it in every project, or to .claude/agents/ inside one project to share it through version control.
- Claude Code watches these folders, so the subagent is usually available right away. Ask Claude to use it by name, or @-mention it to make sure it runs.
Claude Cowork
- Cowork loads subagents through plugins. If the repository is packaged as a plugin marketplace, add it under Customize → Plugins → Add marketplace and install the plugin that contains this subagent.
- Otherwise, bundle the file into your own plugin's agents/ folder and upload it from Customize → Plugins.
New to extending Cowork? Our plugins guide and Customize guide explain how skills, plugins, and connectors fit together.
Inside the source file
An excerpt from plugins/github-dev/agents/pr-comment-resolver.md, shared under the repository's Apache-2.0 license. Read the full file on GitHub.
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
- 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 --json reviews,comments
- Filter to unresolved/pending threads
- 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
- 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
- Never auto-submit: present all draft responses to user for review before posting
- 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))
Before you install
- Read the whole file first. Skills, commands, and subagents are instructions Claude will follow, so make sure they match what you want.
- Check which tools, scripts, or MCP servers it uses. Local servers and scripts run with your permissions.
- Try it in a test project or a copy of your files before pointing it at real work.
- Pin the version you tested, and review changes before updating.
- Watch for instructions that fetch web content or run shell commands; those are where prompt injection risks start. See our prompt injection guide.
FAQ
What is Pr Comment Resolver?
Pr Comment Resolver is a subagent for Claude Code and Claude Cowork from the fcakyon/claude-codex-settings repository on GitHub. 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: 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." User wants to resolve PR review feedback, trigger…
How do I install Pr Comment Resolver in Claude Code?
Download pr-comment-resolver.md from the repository. Save it to ~/.claude/agents/ to use it in every project, or to .claude/agents/ inside one project to share it through version control. Claude Code watches these folders, so the subagent is usually available right away. Ask Claude to use it by name, or @-mention it to make sure it runs.
Can I use Pr Comment Resolver in Claude Cowork?
Cowork loads subagents through plugins. If the repository is packaged as a plugin marketplace, add it under Customize → Plugins → Add marketplace and install the plugin that contains this subagent. Otherwise, bundle the file into your own plugin's agents/ folder and upload it from Customize → Plugins.
Is Pr Comment Resolver safe to install?
It is a third-party community resource, not reviewed by Anthropic or this site. Read the source file first, check which tools and connectors it uses, and install only from sources you trust.
Similar resources
- Web Performance Skills Web performance audits with Core Web Vitals and Chrome DevTools. Plugin · fcakyon/claude-codex-settings
- Ultralytics Dev Ultralytics Platform API and YOLO26 training skills, format hooks, push guard. Plugin · fcakyon/claude-codex-settings
- Tavily Tools Tavily web search and content extraction MCP with hooks for smart tool selection. Plugin · fcakyon/claude-codex-settings
- Stripe Skills Official Stripe skills for checkout, billing, Connect, and API upgrades. Plugin · fcakyon/claude-codex-settings
- Pr Creator Use this agent when you need to create a complete pull request workflow including branch creation, committing staged changes, and PR submission. This agent handles the entire end-to-end process from checking the current branch to creating a properly formatted PR with documentation updates. Examples:\n\n \nContext: User has made code changes and wants to create a PR\nuser: "I've finished… Subagent · fcakyon/claude-codex-settings
- Commit Creator Use this agent when you have staged files ready for commit and need intelligent commit planning and execution. Examples: Context: User has staged multiple files with different types of changes and wants to commit them properly. user: 'I've staged several files with bug fixes and new features. Can you help me commit these?' assistant: 'I'll use the commit-creator agent to analyze your staged… Subagent · fcakyon/claude-codex-settings
- Pr Reviewer Use this agent when user asks to "review a PR", "review pull request", "review this pr", "code review this PR", "check PR #N", or provides a GitHub PR URL for review. Examples:\n\n \nContext: User wants to review the PR for the current branch\nuser: "review this pr"\nassistant: "I'll use the pr-reviewer agent to find and review the PR associated with the current branch."\n \nNo PR number given… Subagent · fcakyon/claude-codex-settings
- Workflow Specialist MUST INVOKE for moai-adk-go SPEC lifecycle work — plan/run/sync phase routing, GEARS/EARS requirement authoring, the 3-phase V3R6 close contract (sync_commit_sha; the completed transition rides the sync commit), Tier S/M/L classification, era classification + grandfather clause, and the Implementation Kickoff Approval human gate before run-phase entry. Covers adding a SPEC and closing one. Subagent · modu-ai/moai-adk