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

コマンドは1行のまま表示されます。コピー前に横へスクロールして全体を確認してください。

ローカルで確認しますか？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

このリポジトリのすべてを見る

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