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

跳到安装

仓库: fcakyon/claude-codex-settings
最近来源活动: 2026年7月10日 21:34
检测到的 SKILL.md 语言: 英语
星标: 1,078
分支: 103

安装方式

默认使用会先检查来源的 Prompt；你也可以切换为直接命令，或下载本地副本。

用 Codex 或 Claude 帮你安装复制这段 Prompt，粘贴到 Codex、Claude 或其他助手里，让它检查 Skill 页面并帮你完成安装。

直接命令不会经过审查 Prompt；运行前请先检查来源。

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

命令会保持在同一行。复制前请横向滚动并检查完整内容。

想先保存到本地？可下载 SkillsMP 当前能够提供的文件。

检查来源文件

决定是否安装前，请先阅读 SKILL.md，以及 SkillsMP 当前展示的配套文件。

SKILL.md

来源说明 · 只读预览

返回搜索返回安装

simplify

This skill should be used when the user asks to "simplify", "clean up the diff", "run simplify", "simplify the changes", "review changed code for cleanup", explicitly invokes "/simplify", or asks to "commit without simplify", "skip simplify for this commit", or "commit this but skip simplify". Reviews changed code across reuse, simplification, efficiency, and altitude, or grants an explicit one-commit bypass. Not for correctness bugs.

2026-08-15

humanize

This skill should be used when writing or revising text, including responses, documentation, comments, emails, posts, reports, and messages, especially when the user asks to "humanize", "write naturally", "remove AI tone", or "avoid AI writing".

2026-08-08

dokploy-deploy

This skill should be used when user asks to "deploy with Dokploy", "use Dokploy Cloud", "manage self-hosted Dokploy", "deploy Docker Compose on Dokploy", "manage Dokploy databases", "configure Dokploy domains", or "look up Dokploy CLI commands".

2026-08-06

查看这个仓库的全部 Skills

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

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