Review PR Comments
latitude-dev/latitude-llm
Triages a PR with GitHub CLI: loads issue-level and inline review feedback (gh pr view, gh api REST, gh api graphql as appropriate), walks items in order, replies in the correct thread, optional…
Draft, confirm, and post replies to GitHub PR review threads.
Install Reply To PR Threads
$ npx skills add tobihagemann/turbo --skill reply-to-pr-threads -a claude-codeProject install by default; add -g for ~/.claude/skills/.
$ gh skill install tobihagemann/turbo reply-to-pr-threads --agent claude-codeProject scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).
$ git clone --depth 1 https://github.com/tobihagemann/turbo.git skills-src && mkdir -p .claude/skills && cp -r skills-src/codex/skills/reply-to-pr-threads .claude/skills/reply-to-pr-threads && rm -rf skills-srcUse ~/.claude/skills/ instead of .claude/skills for a personal install. The folder must contain SKILL.md.
Claude Code skills documentation · loads skills from .claude/skills/
Install the "reply-to-pr-threads" agent skill from https://github.com/tobihagemann/turbo/tree/main/codex/skills/reply-to-pr-threads into .claude/skills/reply-to-pr-threads/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "reply-to-pr-threads", then confirm the skill loads.Claude Code copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$skill-installer install https://github.com/tobihagemann/turbo/tree/main/codex/skills/reply-to-pr-threadsType this inside Codex. $skill-installer <name> installs a curated skill from openai/skills. The installer writes to $CODEX_HOME/skills (default ~/.codex/skills). Restart Codex if the skill does not show up.
$ npx skills add tobihagemann/turbo --skill reply-to-pr-threads -a codexProject install goes to .agents/skills/; add -g for ~/.codex/skills/.
$ gh skill install tobihagemann/turbo reply-to-pr-threads --agent codexProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/tobihagemann/turbo.git skills-src && mkdir -p .agents/skills && cp -r skills-src/codex/skills/reply-to-pr-threads .agents/skills/reply-to-pr-threads && rm -rf skills-srcUse ~/.agents/skills/ instead of .agents/skills for a personal install.
Codex skills documentation · loads skills from .agents/skills/
Install the "reply-to-pr-threads" agent skill from https://github.com/tobihagemann/turbo/tree/main/codex/skills/reply-to-pr-threads into .agents/skills/reply-to-pr-threads/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "reply-to-pr-threads", then confirm the skill loads.Codex copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add tobihagemann/turbo --skill reply-to-pr-threads -a cursorProject install goes to .agents/skills/; add -g for ~/.cursor/skills/.
$ gh skill install tobihagemann/turbo reply-to-pr-threads --agent cursorProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/tobihagemann/turbo.git skills-src && mkdir -p .cursor/skills && cp -r skills-src/codex/skills/reply-to-pr-threads .cursor/skills/reply-to-pr-threads && rm -rf skills-srcUse ~/.cursor/skills/ instead of .cursor/skills for a personal install.
Cursor skills documentation · loads skills from .cursor/skills/, .agents/skills/, .claude/skills/, .codex/skills/
Install the "reply-to-pr-threads" agent skill from https://github.com/tobihagemann/turbo/tree/main/codex/skills/reply-to-pr-threads into .cursor/skills/reply-to-pr-threads/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "reply-to-pr-threads", then confirm the skill loads.Cursor copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gemini skills install https://github.com/tobihagemann/turbo.git --path codex/skills/reply-to-pr-threads--scope user (default) or --scope workspace; --path is the subfolder of the repo that holds the skill; --consent skips the security confirmation prompt.
$ npx skills add tobihagemann/turbo --skill reply-to-pr-threads -a gemini-cliProject install goes to .agents/skills/; add -g for ~/.gemini/skills/.
$ gh skill install tobihagemann/turbo reply-to-pr-threads --agent gemini-cliProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/tobihagemann/turbo.git skills-src && mkdir -p .gemini/skills && cp -r skills-src/codex/skills/reply-to-pr-threads .gemini/skills/reply-to-pr-threads && rm -rf skills-srcUse ~/.gemini/skills/ instead of .gemini/skills for a personal install, then run /skills reload.
Gemini CLI skills documentation · loads skills from .gemini/skills/, .agents/skills/
Install the "reply-to-pr-threads" agent skill from https://github.com/tobihagemann/turbo/tree/main/codex/skills/reply-to-pr-threads into .gemini/skills/reply-to-pr-threads/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "reply-to-pr-threads", then confirm the skill loads.Gemini CLI copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gh skill install tobihagemann/turbo reply-to-pr-threadsInstalls for Copilot at project scope by default; add --scope user for a personal install. Preview a skill first with gh skill preview. Needs GitHub CLI 2.90.0 or later (public preview).
$ npx skills add tobihagemann/turbo --skill reply-to-pr-threads -a github-copilotProject install goes to .agents/skills/; add -g for ~/.copilot/skills/.
$ git clone --depth 1 https://github.com/tobihagemann/turbo.git skills-src && mkdir -p .github/skills && cp -r skills-src/codex/skills/reply-to-pr-threads .github/skills/reply-to-pr-threads && rm -rf skills-srcUse ~/.copilot/skills/ instead of .github/skills for a personal install. Commit .github/skills so cloud agent and code review can use it.
GitHub Copilot skills documentation · loads skills from .github/skills/, .claude/skills/, .agents/skills/
Install the "reply-to-pr-threads" agent skill from https://github.com/tobihagemann/turbo/tree/main/codex/skills/reply-to-pr-threads into .github/skills/reply-to-pr-threads/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "reply-to-pr-threads", then confirm the skill loads.GitHub Copilot copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add tobihagemann/turbo --skill reply-to-pr-threads -a opencodeOpenCode documents no install command of its own. Project install goes to .agents/skills/; add -g for ~/.config/opencode/skills/.
$ gh skill install tobihagemann/turbo reply-to-pr-threads --agent opencodeProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/tobihagemann/turbo.git skills-src && mkdir -p .opencode/skills && cp -r skills-src/codex/skills/reply-to-pr-threads .opencode/skills/reply-to-pr-threads && rm -rf skills-srcUse ~/.config/opencode/skills/ instead of .opencode/skills for a personal install.
OpenCode skills documentation · loads skills from .opencode/skills/, .claude/skills/, .agents/skills/
Install the "reply-to-pr-threads" agent skill from https://github.com/tobihagemann/turbo/tree/main/codex/skills/reply-to-pr-threads into .opencode/skills/reply-to-pr-threads/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "reply-to-pr-threads", then confirm the skill loads.OpenCode copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
Facts
- Skill name
reply-to-pr-threads- GitHub stars
- 408
- Token cost
- ~941 tokens
- SKILL.md length
- 403 words
- Files
- 1
- Skills in repo
- 81
- Repo updated
- First seen
- Licence
- MIT
At a glance
Draft, confirm, and post replies to GitHub PR review threads.
- Works in 5 steps: Re-fetch Thread State → Run $github-voice Skill → Draft Replies → …
- The user asks to reply to PR threads
- SKILL.md covers Step 1: Re-fetch Thread State, Step 2: Run $github-voice Skill, Step 3: Draft Replies and Step 4: Present Drafts and…, plus 2 more sections
- Calls gh
What it does
Reply To PR Threads is an agent skill from tobihagemann/turbo. 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".
Its SKILL.md is about 940 tokens, which your agent loads only when the skill is triggered. It is a single SKILL.md file with no bundled scripts.
It sits in Backend & APIs, covering Pull requests and GraphQL. It works with GitHub and GraphQL. The repository describes itself as: Reusable workflows for planning, building, reviewing, and shipping with Claude Code and Codex. The licence is MIT.
When your agent uses it
- The user asks to reply to PR threads
- Post PR thread replies
- Draft PR reply messages
Example prompts
- “reply to PR threads”
- “post PR thread replies”
- “draft PR reply messages”
- “/reply-to-pr-threads”
Workflow steps
5 steps, taken from the step headings in SKILL.md.
What it can do on your machine
Read from SKILL.md and the folder at commit 931eda5. It shows what the files ask for, not the result of running them.
Tool permissions
Pre-approves nothing: there is no allowed-tools line, so your agent's usual permission prompts apply.
From allowed-tools in the SKILL.md frontmatter.
Runs code
Shell commands in SKILL.md call:
gh
From the folder's file list and the shell code blocks in SKILL.md.
Network
No URLs in SKILL.md. Its commands use gh, which can reach the network depending on how they are called.
From URLs in SKILL.md, links to its own repository left out.
Credentials
Names no API keys, tokens, secrets or passwords.
From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.
Context cost
Reply To PR Threads loads about 941 tokens when it runs. Until then it costs about 80 tokens; SKILL.md has 403 words of instructions outside code blocks.
Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.
Safety
Auto-check passed
The automated check found no risky patterns in SKILL.md.
Automated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); files beside SKILL.md are not scanned.
SKILL.md
The full file from tobihagemann/turbo at commit 931eda5, republished under its MIT licence (© tobihagemann). 403 words, ~941 tokens.
Download SKILL.mdSave it as
.claude/skills/reply-to-pr-threads/SKILL.md (or your agent's skills folder).- name
- 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 session history or mention Codex. 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 request_user_input to ask whether to post. Offer:
- Post — post all drafts as shown
- Cancel — skip posting
Show full SKILL.md (149 more words)Show less
Step 5: Post Replies
For each approved draft, write the drafted reply to .turbo/pr/thread-<thread-id>.md with apply_patch, 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>.mdSubstitute <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 call update_plan to mark this step completed and continue with the next step of the active workflow.
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.
© tobihagemann, MIT. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file
Files
Just SKILL.md in codex/skills/reply-to-pr-threads of tobihagemann/turbo.
Open the folder on GitHubat commit 931eda5
Compare with similar skills
Reply To PR Threads next to the 5 skills that share the most tags, products or categories with it. Stars are the repository's; “used in” counts other GitHub owners with a copy.
| Skill | Stars | Used in | Tokens | Auto-check | Licence | Repo updated |
|---|---|---|---|---|---|---|
| Reply To PR Threads this skilltobihagemann/turbo | 408 | — | ~941 | Automated safety check: Pass | MIT | |
| Review PR Commentslatitude-dev/latitude-llm | 4.7k | — | ~2.6k | Automated safety check: Pass | MIT | |
| GitHub Opsdaymade/claude-code-skills | 1.4k | — | ~3.8k | Automated safety check: Pass | MIT | |
| Gh QueueLanternOps/breeze | 133 | — | ~5k | Automated safety check: Pass | AGPL-3.0 | |
| Create Cuda Python Pull RequestNVIDIA/cuda-python | 3.4k | — | ~1.1k | Automated safety check: Pass | Apache-2.0 | |
| Cuga GitHub Issuescuga-project/cuga-agent | 896 | — | ~1.2k | Automated safety check: Pass | Custom licence |
Similar skills
GitHub Ops
daymade/claude-code-skills
Operates GitHub via gh CLI and REST/GraphQL — PRs, issues, Actions, repos, collaborators, org permissions, 2FA — with explicit target, authorization, and independent readback.
Gh Queue
LanternOps/breeze
A skill your agent uses when reviewing, triaging, or managing the incoming GitHub backlog on the Breeze repo — PRs, Discussions, AND Issues.
- Official
Create Cuda Python Pull Request
NVIDIA/cuda-python
Create a CUDA Python pull request from an approved personal or organization-owned fork, including the GitHub CLI GraphQL fallback for renamed organization-owned forks.
Cuga GitHub Issues
cuga-project/cuga-agent
Create GitHub issues for cuga-agent (bugs, features, epics, designs, and related work) against origin using gh, with epic → feature → issue hierarchy and GraphQL sub-issue linking.
Flow Next Resolve PR
gmickel/flow-next
Resolve PR review feedback. An agent skill from gmickel/flow-next.
More from tobihagemann/turbo
All 81 skills in this repoConsult Oracle
tobihagemann/turbo
Consult ChatGPT Pro via ChatGPT browser automation for problems that resist standard approaches.
Fetch PR Comments
tobihagemann/turbo
Fetch and summarize review feedback and conversation from a GitHub PR (unresolved review threads, review bodies, and PR conversation comments) without making changes.
Recall Rationale
tobihagemann/turbo
Recall why a past change was made by locating the Claude Code transcript that produced it.
Resolve PR Comments
tobihagemann/turbo
Evaluate, fix, answer, and reply to GitHub pull request review comments and conversation comments.
Resolve PR Comments
tobihagemann/turbo
Evaluate, fix, answer, and reply to GitHub pull request review comments and conversation comments.
Assess Technical Debt
tobihagemann/turbo
Assess project-wide structural technical debt: complexity hotspots, deprecated API usage, duplication clusters, architecture rot, and low-value tests.
Related
Categories
Questions about Reply To PR Threads
What does Reply To PR Threads do?
Draft, confirm, and post replies to GitHub PR review threads. Reply To PR Threads is an agent skill from tobihagemann/turbo. Draft, confirm, and post replies to GitHub PR review threads.
When should I use Reply To PR Threads?
Reply To PR Threads fits situations like: the user asks to reply to PR threads; post PR thread replies; draft PR reply messages.
How do I install Reply To PR Threads in Claude Code?
Run `npx skills add tobihagemann/turbo --skill reply-to-pr-threads -a claude-code`. Or copy the skill folder (codex/skills/reply-to-pr-threads in tobihagemann/turbo) into .claude/skills/reply-to-pr-threads in your project. Claude Code loads it when a task matches its description.
How do I install Reply To PR Threads in Codex?
Run `npx skills add tobihagemann/turbo --skill reply-to-pr-threads -a codex`. Or copy the skill folder (codex/skills/reply-to-pr-threads in tobihagemann/turbo) into .agents/skills/reply-to-pr-threads in your project. Codex loads it when a task matches its description.
Can I use Reply To PR Threads in Cursor, Gemini CLI or GitHub Copilot?
Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add tobihagemann/turbo --skill reply-to-pr-threads -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/reply-to-pr-threads, .gemini/skills/reply-to-pr-threads, .github/skills/reply-to-pr-threads and .opencode/skills/reply-to-pr-threads in your project.
What does Reply To PR Threads need to run?
Going by SKILL.md and its folder, Reply To PR Threads needs the command-line tools its instructions call (gh).
Does Reply To PR Threads access the network?
SKILL.md contains no URLs. Its commands use gh, which can reach the network depending on how they are called. This is read from the text; nothing was executed.
Is Reply To PR Threads safe to install?
Our automated static check of SKILL.md found no risky patterns, such as piping downloads into a shell, reading credential files or hidden Unicode. It is not a guarantee. Review the folder before installing.
What licence does Reply To PR Threads use?
Reply To PR Threads is published under the MIT licence (the repository's licence). It allows redistribution, so the full SKILL.md is shown on this page.
How many tokens does Reply To PR Threads use?
About 941 tokens (SKILL.md is roughly 3.8k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full.
What are the alternatives to Reply To PR Threads?
Skills that share tags, products or a category with Reply To PR Threads: Review PR Comments (latitude-dev/latitude-llm, 4.7k stars), GitHub Ops (daymade/claude-code-skills, 1.4k stars), Gh Queue (LanternOps/breeze, 133 stars) and Create Cuda Python Pull Request (NVIDIA/cuda-python, 3.4k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.
Who maintains Reply To PR Threads?
tobihagemann (a GitHub user) maintains it in tobihagemann/turbo, which has 408 GitHub stars. The repository holds 81 skills in this directory. The repository was last updated on October 9, 2026.
Source: tobihagemann/turbo on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.