Loading skill
Install any skill in seconds. Free to start, no credit card required.
Get Started Free →tobihagemann/reply-to-pr-conversation
Draft, confirm, and post a single conversational reply to GitHub PR conversation comments (issue comments). The reply addresses all tracked items in one natural-prose message.
Passed 6 of 15 test cases with the skill, and 7 of 15 without it.
2 fixed7 passed either way10 still failing3 broke
Tokens, turns and time describe resource use, not a dollar price.
One of 2 test cases the skill fixed. Same model, same prompt, with and without the skill.
The reviewer comment includes a code block: ```js const x = 10; ``` Draft a selective quote response for this comment.
| Checked | Without skill | With skill |
|---|---|---|
| Replaces fenced code block lines inside the quote with > [code snippet] | Missed | Passed |
The instructions your model reads when the skill loads.
Draft a single reply that addresses a processed issue-comment list, confirm with the user, and post it as a new PR issue comment.
$github-voice SkillRun the $github-voice skill to load voice rules and the insider-vs-outsider detection.
Use the processed-item list from conversation context. Each entry has: id, author, original comment body (to quote from selectively), category (fix, skip, answer, or clarify), and per-category payload.
Draft one reply that addresses every item as natural conversational prose. The output is a single piece of prose with flexible length and no rigid section structure.
Use the category to interpret each payload:
<sha>" where it fits the flow, plus a brief note when the fix diverges from what the commenter suggested.Quote selectively. Use > blockquotes only for the phrase being responded to. A single-topic reply quotes one sentence then responds; a multi-topic reply weaves quotes and responses together. Drop quotes entirely when @mentions plus context make the reply unambiguous.
Quote handling:
> from quoted lines so nested blockquotes don't misattribute.> [code snippet].[bot], omit the suffix from the @ mention.Apply $github-voice rules. Match the conversation's length and tone. An acknowledgment with emoji is fine when the discussion calls for it; a multi-paragraph response is fine when the items warrant it.
Output the drafted reply as text for review:
**Draft comment**
<full comment body as it will be posted>
test cases passed, vs 7 / 15 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.