pr-comment-resolver

Why this score

This repo hosts 4 subagents, so its 1,181 stars are split between them (about 295 each) for scoring.

Popularity score: 73/100 from public GitHub signals only. It shows how widely used and maintained this is, not how well it works. Not included yet: the fake-star check. The security scan is shown separately and doesn't change the score. How we rank

What it can use

• ! Run shell commands
• ✓ Edit and write files
• ✓ Read and search files

Tools listed in the file: Bash, BashOutput, Glob, Grep, Read, Edit, Write, TodoWrite

Model: inherit

This agent can act outside your files. Read it before installing, and narrow its tools: line if it needs less.

The agent file

---
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))`

Apache-2.0 license, from fcakyon/claude-codex-settings at commit 901ddc10b0aa.

Security

Scanned Oct 21, 2026 at commit 901ddc10b0aa, with Cisco's open-source skill-scanner.

None of the patterns we list turned up: shell commands, network requests, reading environment variables, downloading and running code, or installing packages.

A scan lists patterns in the code. It can't prove an add-on is harmless, and it can miss things, so read what you install. How we scan

Alternatives

Other makers' add-ons that do the same job, next to this one.