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".
SkillScore68Maintained
Automatic
◆Coding pack
Last verified 8/14/2026
What it changes
Passed 12 of 17 test cases with the skill, and 9 of 17 without it.
Without skill55%
With skill68%
Checks it passed that the model alone missed
Starts the reply text with a lowercase letter
Delegates the task to github-dev:pr-comment-resolver
Ensures the first character of the draft reply is lowercase
and 1 more in the full report
4 fixed11 passed either way6 still failing1 broke
Pass-rate lift
+14 pp
Tokens
-23%
Agent turns
0%
Response time
-54%
Model gemini-3.6-flashMeasured 8/14/2026v115 of 22 cases passed with skill · 17 comparable
Tokens, turns and time describe resource use, not a dollar price.
See it in action
One of 4 test cases the skill fixed. Same model, same prompt, with and without the skill.
1 of 4
Prompt
A user named Sarah asked: 'Can we rename this variable to maxRetryCount?' Draft the proposed response.
What was checked, without and with the skill
Checked
Without skill
With skill
Ensures the first character of the draft reply is lowercase
Missed
Passed
case-19 · gemini-3.6-flash · 8/14/2026 · answers are capped and redacted
What's inside
The instructions your model reads when the skill loads.
SKILL.md37 linessingle file
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)).
This skill should be used when user encounters "Azure MCP error", "Azure authentication failed", "az login required", "Azure CLI not found", or needs help configuring Azure MCP integration.