/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".
$ npx -y skills add fcakyon/claude-codex-settings --skill resolve-pr-comments --agent claude-codeHow it fires
How this skill gets triggered: by you, by Claude, or both.
- Fires itselfAuto-invocation. Claude auto-loads it when your prompt matches the work.
- You can call itInvoke it directly when you want it.
- Slash command
/resolve-pr-comments
Context preview
The summary Claude sees to decide when to auto-load this 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".
SKILL.md
resolve-pr-comments.SKILL.mdname: 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))`.
Read more
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))`.
Battle-tested Claude Code, OpenAI Codex, Cursor configs, plugins, hooks and agents with Kimi, MiniMax and GLM API support.
Repo: fcakyon/claude-codex-settings
Other skills on claude-codex-settings.
- /adhd-output-style
This skill should be used when the user asks for "ADHD output", "fewer output tokens", "short numbered steps", "limited working memory formatting", or explicitly invokes "adhd-output-style".
Open skill - /agent-browser
Agent-browser usage guide. Read this before running any agent-browser commands. Covers the snapshot-and-ref workflow, navigating pages, interacting with elements (click, fill, type, select), extracting text and data, taking screenshots, managing tabs, handling forms and auth,
Open skill - /electron
Automate Electron desktop apps (VS Code, Slack, Discord, Figma, Notion, Spotify, etc.) using agent-browser via Chrome DevTools Protocol. Use when the user needs to interact with an Electron app, automate a desktop app, connect to a running app, control a native app, or test an
Open skill - /docx
Use this skill whenever the user wants to create, read, edit, or manipulate Word documents (.docx files) or Word templates (.dotx files). Triggers include: any mention of 'Word doc', 'word document', '.docx', '.dotx', or requests to produce professional documents with formatting
Open skill - /pdf
Use this skill whenever the user wants to do anything with PDF files. This includes reading or extracting text/tables from PDFs, combining or merging multiple PDFs into one, splitting PDFs apart, rotating pages, adding watermarks, creating new PDFs, filling PDF forms,
Open skill - /pptx
Use this skill any time a .pptx or .potx file is involved in any way — as input, output, or both. This includes: creating slide decks, pitch decks, or presentations; reading, parsing, or extracting text from any .pptx or .potx file (even if the extracted content will be used
Open skill

