Claude Cursor Skill

resolve-pr-comments

This skill should be used when user asks to "address PR comments", "resolve PR feedback", "handle review comments", "fix PR issues", "respond to PR review", or explicitly invokes "resolve-pr-comments".

LLM Mart · 0 points · 7 0 0

Virus-scanned Reviewed automatically before listing.

Full trust report

Download fcakyon-claude-codex-settings-plugins_github-dev_skills_resolve-pr-comments-4632eb3.zip · 1 KB

fcakyon/claude-codex-settings 1155 110 forks Apache-2.0 Updated 2d ago

Part of fcakyon/claude-codex-settings — 83 skills

Install

skills CLI npx skills add https://github.com/fcakyon/claude-codex-settings/tree/main/plugins/github-dev/skills/resolve-pr-comments

Claude Code

claude plugin marketplace add https://llmmart.ai/marketplace.json && claude plugin install fcakyon-claude-codex-settings@llmmart

Git git clone https://github.com/fcakyon/claude-codex-settings.git

The skills CLI installs just this skill, for any of its supported agents. Claude Code installs the whole fcakyon/claude-codex-settings collection as a plugin from our marketplace. Git is the plain clone.

Skill manifest

Resolve PR Comments

Analyze unresolved PR review comments, fix valid concerns, and draft responses for comments that do not require code changes.

When explicitly invoked with extra text, treat that text as the PR number or URL. If no PR reference is provided, infer it from the current branch.

Process

Preferred execution
- If subagents are available, use github-dev:pr-comment-resolver and pass the PR reference.
- Otherwise follow the manual steps below.
Fetch unresolved comments
- If a PR number or URL is provided, use it directly.
- Otherwise auto-detect the PR from the current branch with gh pr view --json number,headRefName.
- Fetch inline comments with gh api repos/{owner}/{repo}/pulls/{number}/comments.
- Fetch review-level comments with gh pr view <number> --json reviews,comments.
- Filter to unresolved or pending threads.
Resolve each comment
- If the comment is valid, fix the code and search the codebase for the same problem in other locations.
- Fix all matching occurrences, not just the location mentioned in the comment.
- If the comment does not require a code change, draft a concise reply.
- If the comment is from a bot, reply with a direct factual sentence and no pleasantries.
Reply style
- Start in lowercase.
- Use simple language and short sentences.
- Avoid end punctuation when possible.
- Be concise and polite when replying to real people.
Never auto-submit
- Present all draft responses before posting them.
- Reply comments are posted directly with gh api repos/{owner}/{repo}/pulls/{number}/comments/{comment_id}/replies -f body="..." (the {number} PR number is required, the endpoint 404s without it).
- Add a random 3-5 second delay between posted replies with sleep $((RANDOM % 3 + 3)).

Files (claude-codex-settings)

SKILL.md 2 KB

---
name: resolve-pr-comments
description: This skill should be used when user asks to "address PR comments", "resolve PR feedback", "handle review comments", "fix PR issues", "respond to PR review", or explicitly invokes "resolve-pr-comments".
---

# Resolve PR Comments

Analyze unresolved PR review comments, fix valid concerns, and draft responses for comments
that do not require code changes.

When explicitly invoked with extra text, treat that text as the PR number or URL. If no PR
reference is provided, infer it from the current branch.

## Process

1. **Preferred execution**
   - If subagents are available, use `github-dev:pr-comment-resolver` and pass the PR reference.
   - Otherwise follow the manual steps below.

2. **Fetch unresolved comments**
   - If a PR number or URL is provided, use it directly.
   - Otherwise auto-detect the PR from the current branch with `gh pr view --json number,headRefName`.
   - Fetch inline comments with `gh api repos/{owner}/{repo}/pulls/{number}/comments`.
   - Fetch review-level comments with `gh pr view <number> --json reviews,comments`.
   - Filter to unresolved or pending threads.

3. **Resolve each comment**
   - If the comment is valid, fix the code and search the codebase for the same problem in other locations.
   - Fix all matching occurrences, not just the location mentioned in the comment.
   - If the comment does not require a code change, draft a concise reply.
   - If the comment is from a bot, reply with a direct factual sentence and no pleasantries.

4. **Reply style**
   - Start in lowercase.
   - Use simple language and short sentences.
   - Avoid end punctuation when possible.
   - Be concise and polite when replying to real people.

5. **Never auto-submit**
   - Present all draft responses before posting them.
   - Reply comments are posted directly with `gh api repos/{owner}/{repo}/pulls/{number}/comments/{comment_id}/replies -f body="..."` (the `{number}` PR number is required, the endpoint 404s without it).
   - Add a random 3-5 second delay between posted replies with `sleep $((RANDOM % 3 + 3))`.