reply-to-pr-threads
Draft, confirm, and post replies to GitHub PR review threads, resolving those whose entry carries a resolution reason
Install / Use
npx skills add tobihagemann/turbo --skill reply-to-pr-threadsInstalls into whichever agent you are using.
SKILL.md
Installable skill definition
Quality Score
Category
MarketingSupported Platforms
Our assessment of reply-to-pr-threads
reply-to-pr-threads scores 84/100 on our quality scale, 496th of 649 Marketing skills we index.
Its SKILL.md is 3.6 KB long, well organised into 8 sections with 4 code examples: a solid amount of guidance for an agent.
It has 405 GitHub stars, a meaningful sign that others use it.
Maintenance, license and trust
- The repository was last updated about 2 months ago, so reply-to-pr-threads is actively maintained.
- Our last check on 2026-11-02 found the source still online.
- It is released under the MIT license, a permissive license that allows use, modification and commercial use with attribution.
- Its trust signals score 100/100, with no cautions. These come from repository metadata, not a code audit — read the skill file before letting an agent act on it.
Safety scan
No issues foundOur scan of the whole file found no instruction hijacking, hidden characters, credential access, data exfiltration or destructive commands. An AI review of the same text found nothing harmful.
AI review by kimi-k2.7-code on 2026-10-05. Automated pattern scan on 2026-10-05. It catches known dangerous patterns, not every risk — read a skill before letting an agent act on it.
reply-to-pr-threads compared with similar skills
All 4 of these similar skills score higher than reply-to-pr-threads; compare them before choosing.
| Skill | Score | Stars | Updated | Format |
|---|---|---|---|---|
| reply-to-pr-threads (this skill)by tobihagemann | 84 | 405 | 57d ago | SKILL.md |
| Agent-Reachby Panniantong | 100 | 113.3k | 12d ago | CLAUDE.md |
| algorithmic-artby anthropics | 100 | 177.9k | 58d ago | SKILL.md |
| pptxby anthropics | 100 | 177.9k | 58d ago | SKILL.md |
| prospectingby coreyhaines31 | 100 | 60.1k | 8d ago | SKILL.md |
Frequently asked questions
- How do I install reply-to-pr-threads?
- Run
npx skills add tobihagemann/turbo --skill reply-to-pr-threads. The install tabs above show the steps for each supported agent. - Which AI agents does reply-to-pr-threads work with?
- It is written for Universal, as a SKILL.md file. Other agents that read the same format can often use it too.
- Is reply-to-pr-threads safe to use?
- Our scan of the whole file found no instruction hijacking, hidden characters, credential access, data exfiltration or destructive commands. An AI review of the same text found nothing harmful. It is MIT-licensed and scores 100/100 on trust signals. Skills are instructions an agent will follow, so read the file before installing it and do not approve commands you do not understand.
- Is reply-to-pr-threads still maintained?
- The repository was last updated about 2 months ago, so reply-to-pr-threads is actively maintained.
Skill content
View source on GitHubname: reply-to-pr-threads description: "Draft, confirm, and post replies to GitHub PR review threads. Handles per-category reply formatting, re-fetches thread resolution state so auto-resolved threads are skipped, and posts via GraphQL. Use when the user asks to "reply to PR threads", "post PR thread replies", or "draft PR reply messages"."
Reply to PR Threads
Draft replies for a processed review-thread list, confirm with the user, and post the surviving drafts.
Step 1: Re-fetch Thread State
Auto-detect owner, repo, and PR number from the current branch if not provided, then query the current resolution state:
gh api graphql -f query='
query($owner: String!, $repo: String!, $pr: Int!) {
repository(owner: $owner, name: $repo) {
pullRequest(number: $pr) {
reviewThreads(first: 100) {
nodes { id isResolved }
}
}
}
}' -f owner='{owner}' -f repo='{repo}' -F pr={pr_number}
Drop threads whose isResolved is now true. Reviewers or bots such as CodeRabbit may resolve threads after the original fetch, and drafting replies for them is wasted work.
Step 2: Run /github-voice Skill
Run the /github-voice skill to load voice rules and the insider-vs-outsider detection.
Step 3: Draft Replies
Use the processed-thread list from conversation context. Each entry has: thread id, file path, line, category (fix, skip, answer, or clarify), and per-category payload.
Keep every reply to one or two sentences. No bullet-point reasoning. No bolded labels.
fix: payload is a commit SHA, optionally with a divergence note.
Fixed in <commit-sha>.
Only add a brief sentence after the SHA when the fix meaningfully diverges from what the reviewer suggested. Otherwise the SHA alone is enough.
skip: payload is the skip reasoning. State the reasoning directly. Do not apologize.
answer: payload is the raw answer text. Tighten to one or two sentences and apply /github-voice rules. Do not cite transcripts or mention Claude. The reply reads as the implementer's own explanation.
clarify: payload is a user-directed question. Draft it as directed.
Step 4: Present Drafts and Confirm
Output all drafts as text, grouped by file:
### <file-path>
**Thread <id>** (<category>, line <line>)
Reviewer: <original comment, truncated if long>
Reply: <drafted reply>
Then use AskUserQuestion to ask whether to post. Offer:
- Post — post all drafts as shown
- Cancel — skip posting
Step 5: Post Replies
For each approved draft, write the drafted reply to .turbo/pr/thread-<thread-id>.md with the Write tool, then post via the reply mutation:
gh api graphql -f query='
mutation($threadId: ID!, $body: String!) {
addPullRequestReviewThreadReply(input: {pullRequestReviewThreadId: $threadId, body: $body}) {
comment { id }
}
}' -f threadId='<thread-id>' -F body=@.turbo/pr/thread-<thread-id>.md
Substitute <thread-id> with the thread's id for each post.
Report the outcome as a table, one row per thread, keeping every cell to a single line:
| Thread | Category | Outcome | |--------|----------|---------|
Where Outcome is one of:
- Posted — the reply was posted
- Skipped — name the reason, such as auto-resolution between the re-fetch and the post
Keep the report to the table. When the table would be empty, report one line stating that no replies were posted and why instead.
Then use the TaskList tool and proceed to any remaining task.
Rules
- Never resolve or dismiss a review thread. Only reply. Let the reviewer resolve.
- If a post mutation fails because the thread is already resolved, log the skip and continue with the rest.
Related Skills
Agent-Reach
113.3kGive your AI agent eyes to see the entire internet. Read & search Twitter, Reddit, YouTube, GitHub, Bilibili, XiaoHongShu — one CLI, zero API fees.
algorithmic-art
177.9kCreating algorithmic art using p5.js with seeded randomness and interactive parameter exploration. Use this when users request creating art using code, generative art, algorithmic art, flow fields, or particle systems.
pptx
177.9kUse this skill any time a .pptx or .potx file is involved in any way — as input, output, or both. This includes: creating slide decks, pitch decks, or presentations; reading, parsing, or extracting text from any .pptx or .potx file (even if the extracted content will be used elsewhere, like in an em…
prospecting
60.1kWhen the user wants to find and qualify prospects for outbound, or asks who to target first, which signal to prioritize, or where to spot buyers with the problem: buying signals, enrichment, verification, account research.
Languages
Trust signals
From repository metadata: license, adoption, age and documentation. Not a code audit — see the Safety scan above for what the skill file itself contains.
