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".
Works with
---
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".
license: Apache-2.0
---
# 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))`.More Code Review skills
pr-to-video
heygen-com/hyperframes
Turn a GitHub pull request (a PR URL, owner/repo#N, or 'this PR' in a checked-out repo) into a code-change explainer video — changelog, feature reveal, fix, or refactor walkthrough built from the diff, commits, and files: the input is a code change, not a website. Not a product promo (/product-launch-video) or a no-PR topic explainer (/faceless-explainer). Unclear → /hyperframes.
receiving-code-review
obra/superpowers
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
public-relations
coreyhaines31/marketingskills
When the user wants help with public relations, earned media, press coverage, journalist outreach, or media strategy (not pull requests). Also use when the user mentions 'PR,' 'public relations,' 'press,' 'press release,' 'press coverage,' 'media outreach,' 'pitch a journalist,' 'get featured,' 'media list,' 'media kit,' 'press kit,' 'newsjacking,' 'news hijack,' 'HARO,' 'Qwoted,' 'Featured,' 'Help A Reporter,' 'reporter request,' 'tech press,' 'TechCrunch,' 'earned media,' 'thought leadership placement,' 'op-ed,' 'guest article,' 'press contacts,' 'podcast prep,' 'going on a podcast,' 'podcast guest,' 'prep me for this podcast,' or 'how do I get press.' Use this for earned media work — finding journalists, pitching stories, newsjacking, prepping podcast appearances, and responding to press requests. For startup/SaaS/AI directory submissions, see directory-submissions. For product launches, see launch. For social-media engagement, see social. For cold-email outreach to prospects, see cold-email.
