reply-to-pr-conversation SKILL.md skillA
reply-to-pr-conversation from tobihagemann/turbo is an agent skill: a SKILL.md folder an AI agent loads when a task calls for it.
mdr add tobihagemann/turbo/reply-to-pr-conversation@git:20260708.cc413e5Pins git:20260708.cc413e5 in mdr.lock. Pin the fingerprint instead.
- Audit grade
- A, 17 of 17 checks passed
- Kind
- SKILL.md skill
- Repository
- tobihagemann/turbo
- Path
claude/skills/reply-to-pr-conversation/SKILL.md- Versions recorded
- 3
- Latest version
- git:20260708.cc413e5, committed Jul 8, 2026
- First version recorded
- May 8, 2026
- Size
- 3,170 bytes
- Repository stars
- 418
- License
- MIT
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".
Collected from public GitHub. Every version is saved exactly as it was and never changes. Install it at an exact version with the mdr tool, and every file is checked before it reaches your agent. The main file is checked against the SHA-256 fingerprint recorded here, and the others against the fingerprints GitHub keeps for its source commit. The automatic checks below grade the latest version, and the same checks always give the same file the same grade.
What the file says
# 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. …
Read the whole file at its exact version.
How to install
mdr add tobihagemann/turbo/reply-to-pr-conversation@sha256:9a75e79a4ceee430The line at the top of this page pins the label git:20260708.cc413e5, which is what most people want. This one pins the sha256 fingerprint of the contents instead, so it survives a label being moved. Either way the exact version is written to mdr.lock, and mdr install downloads and checks those contents again, so it installs them exactly or stops with an error.
[](https://markdownregistry.com/a/art_c24ntqgwjbme6zgx)
3 badge image fetches in 30 days. What the badge shows.
Versions
The registry has recorded 3 versions of this file, between May 8, 2026 and Jul 8, 2026, about one every 31 days.
| version | committed | commit | size | audit | |
|---|---|---|---|---|---|
| git:20260708.cc413e5 latest | 2026-07-08 | cc413e5 | 3,170 B | A | view · diff |
| git:20260528.9ba856f | 2026-05-28 | 9ba856f | 3,146 B | A | view · diff |
| git:20260508.4249183 | 2026-05-08 | 4249183 | 3,088 B | A | view |
Audit of the latest version
- pass: Frontmatter block present
- pass: Frontmatter declares a name
- pass: Frontmatter declares a description
- pass: Size between 200 bytes and 200 KB (3170 bytes)
- pass: No zero-width or bidi control characters
- pass: No instruction hidden inside an HTML comment
- pass: No link to an exfiltration or paste host
- pass: No credential-shaped string
- pass: No instruction to send local credentials anywhere
- pass: No text hidden with inline styles
- pass: No prompt-injection phrasing
- pass: No curl or wget piped into a shell
- pass: No recursive delete of root, home or parent
- pass: No instruction to read or print local credentials
- pass: No base64 blob over 200 characters
- pass: No link to a raw IP address
- pass: No script tag
Source
tobihagemann/turbo · 418 stars · license MIT · pushed 2026-10-23 · branch main
API
GET https://markdownregistry.com/api/v1/artifacts/art_c24ntqgwjbme6zgx GET https://markdownregistry.com/api/v1/resolve?ref=tobihagemann/turbo/reply-to-pr-conversation GET https://markdownregistry.com/api/v1/blob/9a75e79a4ceee43059ccc3eb6140d0d6976a73897784879a8e12992f96ddbc2b
Your AI assistant does the legwork. You hear about the deals worth your word. Hand yours the standing instructions at modelranch.com and it joins the network that reads files like this one.
Guides: the SKILL.md format and its required fields · what to check before you install a skill · how to pin a skill to an exact version · where to find agent skills · keeping a team on the same skills · which agent file does what.
More from tobihagemann/turbo
Every file in tobihagemann/turbo