tobihagemann/reply-to-pr-conversation
claude/skills/reply-to-pr-conversation/SKILL.md
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. Use when the user asks to "reply to PR conversation", "post PR conversation replies", or "draft PR conversation messages".
$ install --global
skillsauthnpx skillsauth add tobihagemann/turbo reply-to-pr-conversationInstall this skill globally with one command. Works with Claude Code, Cursor, and Windsurf.
Security Scan Results
3 of 9 scanners reported clean
Some scanners were skipped, did not run, or reported a non-clean status. Review each row below.
3
Scanners Passed
9
Scanners in report
Clean
TrivyContainer and dependency vulnerability scanner
95%
Clean
SemgrepStatic code analysis for vulnerabilities
95%
Clean
mcp-scan (Snyk)Model Context Protocol security validation
95%
Skipped
Snyk (dep)Open source security scanning
50%
Skipped
Socket.devSupply chain security analysis
50%
Skipped
VirusTotalMulti-engine malware detection
50%
Skipped
CrowdStrikeAdvanced threat intelligence
50%
Skipped
OSV-ScannerOpen Source Vulnerability database check
50%
Skipped
OWASP Dep-Check
50%
Last scanned: May 29, 2026, 4:27 AM77.5s1 file scanned
SKILL.md
- name:
- reply-to-pr-conversation
- description:
- 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. Use when the user asks to \"reply to PR conversation\", \"post PR conversation replies\", or \"draft PR conversation messages\".
Reply to PR Conversation
Draft a single reply that addresses a processed issue-comment list, confirm with the user, and post it as a new PR issue comment.
Step 1: Run /github-voice Skill
Run the /github-voice skill to load voice rules and the insider-vs-outsider detection.
Step 2: Compose the Reply
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:
- fix: payload is a commit SHA. Mention "fixed in
<sha>" where it fits the flow, plus a brief note when the fix diverges from what the commenter suggested. - skip: payload is the skip reasoning. State it directly.
- answer: payload is answer text prepared upstream. Integrate it as the implementer's own words.
- clarify: payload is a user-directed question. Ask it as-is.
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:
- Strip leading
>from quoted lines so nested blockquotes don't misattribute. - Replace fenced-code lines inside a quote with
> [code snippet]. - If the author login ends in
[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.
Step 3: Confirm
Output the drafted reply as text for review:
**Draft comment**
<full comment body as it will be posted>
Then use AskUserQuestion to ask whether to post. Offer:
- Post — post the comment
- Cancel — skip posting
Step 4: Post the Comment
Auto-detect owner, repo, and PR number from the current branch if not provided. Write the drafted body to .turbo/pr/comment.md with the Write tool, then post via the issue-comments REST endpoint:
gh api -X POST \
"/repos/<owner>/<repo>/issues/<pr_number>/comments" \
-F [email protected]/pr/comment.md
Report the posted comment's URL.
Then use the TaskList tool and proceed to any remaining task.
Rules
- Never close the PR, resolve a thread, or edit existing comments. Only post a new issue comment.
- If the post fails, report the failure and leave the drafted body in the output so the user can post it manually.
Related Skills
tobihagemann/finalize
development
VerifiedTrustedCommunity
Run the post-implementation quality assurance workflow including tests, code polishing, review, and commit. Use when the user asks to "finalize implementation", "finalize changes", "wrap up implementation", "finish up", "ready to commit", or "run QA workflow".
331SKILL.mdUpdated May 9, 2026
tobihagemann/finalize
development
VerifiedTrustedCommunity
Run the post-implementation quality assurance workflow including tests, code polishing, review, and commit. Use when the user asks to "finalize implementation", "finalize changes", "wrap up implementation", "finish up", "ready to commit", or "run QA workflow".
331SKILL.mdUpdated May 9, 2026
tobihagemann/understand-change
tools
VerifiedTrustedCommunity
Teach the user to deeply understand a change through interactive tutoring: restating understanding, drilling into why/what/how, and quizzing until mastery. The active counterpart to a one-shot explanation. Use when the user asks to "understand this change", "teach me this change", "help me understand what changed", "walk me through this change", "make sure I understand this", "quiz me on this", or "teach me what we did".
319SKILL.mdUpdated Jun 4, 2026
tobihagemann/understand-change
tools
VerifiedTrustedCommunity
Teach the user to deeply understand a change through interactive tutoring: restating understanding, drilling into why/what/how, and quizzing until mastery. The active counterpart to a one-shot explanation. Use when the user asks to "understand this change", "teach me this change", "help me understand what changed", "walk me through this change", "make sure I understand this", "quiz me on this", or "teach me what we did".
319SKILL.mdUpdated Jun 4, 2026