resolve-pr-comments
The resolve-pr-comments skill analyzes unresolved GitHub pull request review comments, implements fixes for valid code concerns across the codebase, and drafts responses for comments requiring no code changes. Use it when asked to address PR feedback, handle review comments, or resolve PR issues, optionally providing a PR number or URL for the skill to process.
git clone --depth 1 https://github.com/fcakyon/claude-codex-settings /tmp/resolve-pr-comments && cp -r /tmp/resolve-pr-comments/plugins/github-dev/skills/resolve-pr-comments ~/.claude/skills/resolve-pr-commentsSKILL.md
# 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/comments/{comment_id}/replies -f body="..."`.
- Add a random 3-5 second delay between posted replies with `sleep $((RANDOM % 3 + 3))`.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, waiting for content, running multiple browser sessions in parallel, and troubleshooting common failures. Use when the user asks to interact with a website, fill a form, click something, extract data, take a screenshot, log into a site, test a web app, or automate any browser task.
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 Electron application. Triggers include "automate Slack app", "control VS Code", "interact with Discord app", "test this Electron app", "connect to desktop app", or any task requiring automation of a native Electron application.
Use this skill whenever the user wants to create, read, edit, or manipulate Word documents (.docx files). Triggers include: any mention of 'Word doc', 'word document', '.docx', or requests to produce professional documents with formatting like tables of contents, headings, page numbers, or letterheads. Also use when extracting or reorganizing content from .docx files, inserting or replacing images in documents, performing find-and-replace in Word files, working with tracked changes or comments, or converting content into a polished Word document. If the user asks for a 'report', 'memo', 'letter', 'template', or similar deliverable as a Word or .docx file, use this skill. Do NOT use for PDFs, spreadsheets, Google Docs, or general coding tasks unrelated to document generation.
Use when tasks involve reading, creating, or reviewing PDF files where rendering and layout matter; prefer visual checks by rendering pages (Poppler) and use Python tools such as `reportlab`, `pdfplumber`, and `pypdf` for generation and extraction.
Use this skill any time a .pptx 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 file (even if the extracted content will be used elsewhere, like in an email or summary); editing, modifying, or updating existing presentations; combining or splitting slide files; working with templates, layouts, speaker notes, or comments. Trigger whenever the user mentions \"deck,\" \"slides,\" \"presentation,\" or references a .pptx filename, regardless of what they plan to do with the content afterward. If a .pptx file needs to be opened, created, or touched, use this skill.
Use this skill any time a spreadsheet file is the primary input or output. This means any task where the user wants to: open, read, edit, or fix an existing .xlsx, .xlsm, .csv, or .tsv file (e.g., adding columns, computing formulas, formatting, charting, cleaning messy data); create a new spreadsheet from scratch or from other data sources; or convert between tabular file formats. Trigger especially when the user references a spreadsheet file by name or path — even casually (like \"the xlsx in my downloads\") — and wants something done to it or produced from it. Also trigger for cleaning or restructuring messy tabular data files (malformed rows, misplaced headers, junk data) into proper spreadsheets. The deliverable must be a spreadsheet file. Do NOT trigger when the primary deliverable is a Word document, HTML report, standalone Python script, database pipeline, or Google Sheets API integration, even if tabular data is involved.
This skill should be used when user asks to "query Azure resources", "list storage accounts", "manage Key Vault secrets", "work with Cosmos DB", "check AKS clusters", "use Azure MCP", or interact with any Azure service.
This skill should be used when user encounters "Tavily MCP error", "Tavily API key invalid", "web search not working", "Tavily failed", or needs help configuring Tavily integration.