Loading skill
Install any skill in seconds. Free to start, no credit card required.
Get Started Free →tobihagemann/resolve-pr-comments
Evaluate, fix, answer, and reply to GitHub pull request review comments and conversation comments. Handles both change requests (fix or skip) and reviewer questions (explain using reasoning recalled from past Claude Code transcripts).
Passed 15 of 20 test cases with the skill, and 11 of 20 without it.
and 9 more in the full report
8 fixed10 passed either way3 still failing3 broke
Tokens, turns and time describe resource use, not a dollar price.
One of 8 test cases the skill fixed. Same model, same prompt, with and without the skill.
A reviewer asked a clarification question as a PR conversation issue comment. Should this question be passed to `$answer-reviewer-questions` in Step 9 alongside inline-thread questions?
| Checked | Without skill | With skill |
|---|---|---|
| Excludes issue-comment questions from Step 9 execution. | Missed | Passed |
| Composes answers for issue-comment questions during Step 11 PR conversation assembly. | Missed | Passed |
The instructions your model reads when the skill loads.
Fetch unresolved review comments from a GitHub PR (inline threads, review-body observations, and issue-comment observations from the PR conversation), evaluate each one, fix or skip based on confidence, answer reviewer questions using recalled implementation reasoning, and reply. Inline threads are answered with thread replies; issue-comment findings are answered with new PR conversation comments. Review-body findings flow through the same evaluate-and-fix pipeline; their outcomes land in the summary because a review body has no destination to post to.
At the start, use update_plan to track each step, restating any remaining steps of a parent workflow alongside them:
$interpret-feedback skill$evaluate-findings skill$resolve-findings skill$answer-reviewer-questions skill$reply-to-pr-threads skill$reply-to-pr-conversation skillAuto-detect owner, repo, and PR number from current branch if not provided. Then run scripts/fetch-pr-data.sh, which handles full pagination (reviews, review threads, inner comment pages for long threads, issue comments, commits) and emits a single merged JSON document:
bash <skill-dir>/scripts/fetch-pr-data.sh <owner> <repo> <pr_number>
Output shape:
{
"meta": { "title", "url", "headRefName", "baseRefName" },
"reviewThreads": [ { "id", "isResolved", "isOutdated", "comments": { "nodes": [ { "author", "body", "path", "line", "originalLine", "diffHunk" } ] } } ],
"reviews": [ { "author", "body", "state", "submittedAt" } ],
"issueComments": [ { "author", "body", "createdAt", "url" } ],
"commits": [ { "commit": { "oid", "abbreviatedOid", "message", "committedDate" } } ]
}
test cases passed, vs 11 / 20 without
Published skills whose descriptions closely match this one, with their headline benchmark lift.
More skills from the same source and nearby in the registry, with their headline benchmark lift.