Resolve Pr Comments Agent Skill

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".

524 tokens

context cost

the whole folder, loaded on every use

files

instructions only

copies elsewhere

how many repositories repackaged it

955

stars on the repo

on the repository, not the skill itself

Install

one command, takes just this skill from the repository

npx skills add https://github.com/fcakyon/claude-codex-settings --skill resolve-pr-comments

The instruction itself

2 sections, as written by the author

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

Other skills for the same job

different authors, same section of the catalogue

Receiving Code Review

by ZhanlinCui

×7

Use when receiving code review feedback, before implementing suggestions, especially if feedback seems unclear or technically questionable - requires technical rigor and verification, not performative agreement or blind implementation

2k tokens

Requesting Code Review

by ZhanlinCui

×6

Use when completing tasks, implementing major features, or before merging to verify work meets requirements

Execute git commit with conventional commit message analysis, intelligent staging, and message generation. Use when user asks to commit changes, create a git commit, or mentions "/commit". Supports: (1) Auto-detecting type and scope from changes, (2) Generating conventional commit messages from diff, (3) Interactive commit with optional type/scope/description overrides, (4) Intelligent file staging for logical grouping

Comprehensive GitHub code review with AI-powered swarm coordination

Behavioral guidelines to reduce common LLM coding mistakes. Use when writing, reviewing, or refactoring code to avoid overcomplication, make surgical changes, surface assumptions, and define verifiable success criteria.

Use this skill to review code. It supports both local changes (staged or working tree) and remote Pull Requests (by ID or URL). It focuses on correctness, maintainability, and adherence to project standards.

Refactor bloated AGENTS.md, CLAUDE.md, or similar agent instruction files to follow progressive disclosure principles. Splits monolithic files into organized, linked documentation.

Create high-quality git commits: review/stage intended changes, split into logical commits, and write clear commit messages (including Conventional Commits). Use when the user asks to commit, craft a commit message, stage changes, or split work into multiple commits.

2k tokens

How to use it

Copy the folder

Take fcakyon/resolve-pr-comments from the repository into ~/.claude/skills for personal use, or into .claude/skills inside a project.

Check the name does not clash

The agent identifies a skill by the name field in its header. Two skills with the same name cannot sit side by side — one of them will be ignored.