New: 98,000+ skills indexed from GitHub repos with 100+ stars · every skill safety-checkedBrowse top skillsTop skills
Esc to closeBrowse all skills
Submit a skillBrowse skills
Submit a skillBrowse skills

Agent skill

Reply To PR Conversation

by tobihagemann in tobihagemann/turbo

Draft, confirm, and post a single conversational reply to GitHub PR conversation comments (issue comments).

MITAuto-check passed

Install Reply To PR Conversation

skills CLI
$ npx skills add tobihagemann/turbo --skill reply-to-pr-conversation -a claude-code

Project install by default; add -g for ~/.claude/skills/.

GitHub CLI
$ gh skill install tobihagemann/turbo reply-to-pr-conversation --agent claude-code

Project scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).

Manual copy
$ 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-conversation .claude/skills/reply-to-pr-conversation && rm -rf skills-src

Use ~/.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/

Facts

Skill name
reply-to-pr-conversation
GitHub stars
408
Token cost
~804 tokens
SKILL.md length
397 words
Files
1
Skills in repo
81
Repo updated
First seen
Licence
MIT

At a glance

Draft, confirm, and post a single conversational reply to GitHub PR conversation comments (issue comments).

  • Works in 4 steps: Run $github-voice Skill → Compose the Reply → Confirm → …
  • The user asks to reply to PR conversation
  • SKILL.md covers Step 1: Run $github-voice Skill, Step 2: Compose the Reply, Step 3: Confirm and Step 4: Post the Comment, plus 1 more section
  • Calls gh

What it does

Reply To PR Conversation is an agent skill from tobihagemann/turbo. 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".

Its SKILL.md is about 800 tokens, which your agent loads only when the skill is triggered. It is a single SKILL.md file with no bundled scripts.

It works with GitHub. 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 conversation
  • Post PR conversation replies
  • Draft PR conversation messages

Example prompts

  • “reply to PR conversation”
  • “post PR conversation replies”
  • “draft PR conversation messages”
  • “/reply-to-pr-conversation”

Workflow steps

4 steps, taken from the step headings in SKILL.md.

  1. Run $github-voice Skill
  2. Compose the Reply
  3. Confirm
  4. Post the Comment

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 Conversation loads about 804 tokens when it runs. Until then it costs about 81 tokens; SKILL.md has 397 words of instructions outside code blocks.

Always · name and description, kept in context so the agent knows when to use it
~81
When it runs · the whole SKILL.md, loaded when a task matches
~804

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). 397 words, ~804 tokens.

Download SKILL.mdSave it as .claude/skills/reply-to-pr-conversation/SKILL.md (or your agent's skills folder).
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.

Show full SKILL.md (123 more words)Show less

Step 3: Confirm

Output the drafted reply as text for review:

**Draft comment**

<full comment body as it will be posted>

Then use request_user_input 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/<pr_number>-comment.md with apply_patch, then post via the issue-comments REST endpoint:

bash
gh api -X POST \
  "/repos/<owner>/<repo>/issues/<pr_number>/comments" \
  -F body=@.turbo/pr/<pr_number>-comment.md

Report the posted comment's URL.

Then call update_plan to mark this step completed and continue with the next step of the active workflow.

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.

© 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-conversation of tobihagemann/turbo.

Open the folder on GitHubat commit 931eda5

Compare with similar skills

Reply To PR Conversation 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.

Reply To PR Conversation compared with similar skills
SkillStarsUsed inTokensAuto-checkLicenceRepo updated
Reply To PR Conversation this skilltobihagemann/turbo408—~804Automated safety check: PassMIT
PR Babysitteropeninterpreter/openinterpreter69k3 repos~4.2kAutomated safety check: PassApache-2.0
Greplooponyx-dot-app/onyx32k4 repos~3.3kAutomated safety check: PassMIT
GitHub Deep Researchbytedance/deer-flow84k4 repos~1.3kAutomated safety check: PassMIT
Diagnosing Superpowers Sessionsobra/superpowers297k3 repos~1.7kAutomated safety check: PassMIT
Update V8 Versionopeninterpreter/openinterpreter69k2 repos~845Automated safety check: PassApache-2.0

Similar skills

  • PR Babysitter

    openinterpreter/openinterpreter

    Watches an open GitHub pull request until it merges, handling review comments, diagnosing CI failures and retrying flaky checks along the way.

    69k GitHub starsUsed in 3 repos~4.2k tokens
    DevelopmentAuto-check passed

  • Greploop

    onyx-dot-app/onyx

    Iteratively improves a PR (GitHub), MR (GitLab), or shelved changelist (Perforce) until Greptile gives it a 5/5 confidence score with zero unresolved comments.

    32k GitHub starsUsed in 4 repos~3.3k tokens
    DevelopmentAuto-check passed

  • GitHub Deep Research

    bytedance/deer-flow

    Researches a GitHub repository over four rounds using the GitHub API and web search, then writes a structured markdown report with timeline, metrics and Mermaid diagrams.

    84k GitHub starsUsed in 4 repos~1.3k tokens
    Research & ScienceAuto-check passed

  • Diagnosing Superpowers Sessions

    obra/superpowers

    Investigates a session where Superpowers went wrong, reads the transcripts on disk and produces an evidence-cited report, optionally prepared as a bug report for the maintainers.

    297k GitHub starsUsed in 3 repos~1.7k tokens
    Agent WorkflowsAuto-check passed

  • Update V8 Version

    openinterpreter/openinterpreter

    Bumps the pinned v8 and rusty_v8 versions in Codex, validates the release-candidate path with the v8-canary check, and traces failures to upstream build changes.

    69k GitHub starsUsed in 2 repos~845 tokens
    DevOps & CloudAuto-check passed

  • Last30days

    mvanhorn/last30days-skill

    Research what people actually say about any topic in the last 30 days.

    64k GitHub stars~7.9k tokensUpdated yesterday
    Research & ScienceAuto-check: notes

More from tobihagemann/turbo

All 81 skills in this repo

  • Consult Oracle

    tobihagemann/turbo

    Consult ChatGPT Pro via ChatGPT browser automation for problems that resist standard approaches.

    408 GitHub stars~1.1k tokensUpdated 2 days ago
    Auto-check passed

  • 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.

    408 GitHub stars~967 tokensUpdated 2 days ago
    Auto-check passed

  • Recall Rationale

    tobihagemann/turbo

    Recall why a past change was made by locating the Claude Code transcript that produced it.

    408 GitHub stars~1.3k tokensUpdated 2 days ago
    Auto-check passed

  • Resolve PR Comments

    tobihagemann/turbo

    Evaluate, fix, answer, and reply to GitHub pull request review comments and conversation comments.

    408 GitHub stars~3.8k tokensUpdated 2 days ago
    Auto-check passed

  • Resolve PR Comments

    tobihagemann/turbo

    Evaluate, fix, answer, and reply to GitHub pull request review comments and conversation comments.

    408 GitHub stars~3.8k tokensUpdated 2 days ago
    Auto-check passed

  • Assess Technical Debt

    tobihagemann/turbo

    Assess project-wide structural technical debt: complexity hotspots, deprecated API usage, duplication clusters, architecture rot, and low-value tests.

    408 GitHub stars~2.8k tokensUpdated 2 days ago
    Auto-check passed

Works with

Questions about Reply To PR Conversation

What does Reply To PR Conversation do?

Draft, confirm, and post a single conversational reply to GitHub PR conversation comments (issue comments). Reply To PR Conversation is an agent skill from tobihagemann/turbo. Draft, confirm, and post a single conversational reply to GitHub PR conversation comments (issue comments).

When should I use Reply To PR Conversation?

Reply To PR Conversation fits situations like: the user asks to reply to PR conversation; post PR conversation replies; draft PR conversation messages.

How do I install Reply To PR Conversation in Claude Code?

Run `npx skills add tobihagemann/turbo --skill reply-to-pr-conversation -a claude-code`. Or copy the skill folder (codex/skills/reply-to-pr-conversation in tobihagemann/turbo) into .claude/skills/reply-to-pr-conversation in your project. Claude Code loads it when a task matches its description.

How do I install Reply To PR Conversation in Codex?

Run `npx skills add tobihagemann/turbo --skill reply-to-pr-conversation -a codex`. Or copy the skill folder (codex/skills/reply-to-pr-conversation in tobihagemann/turbo) into .agents/skills/reply-to-pr-conversation in your project. Codex loads it when a task matches its description.

Can I use Reply To PR Conversation 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-conversation -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-conversation, .gemini/skills/reply-to-pr-conversation, .github/skills/reply-to-pr-conversation and .opencode/skills/reply-to-pr-conversation in your project.

What does Reply To PR Conversation need to run?

Going by SKILL.md and its folder, Reply To PR Conversation needs the command-line tools its instructions call (gh).

Does Reply To PR Conversation 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 Conversation 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 Conversation use?

Reply To PR Conversation 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 Conversation use?

About 804 tokens (SKILL.md is roughly 3.2k 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 Conversation?

Skills that share tags, products or a category with Reply To PR Conversation: PR Babysitter (openinterpreter/openinterpreter, 69k stars), Greploop (onyx-dot-app/onyx, 32k stars), GitHub Deep Research (bytedance/deer-flow, 84k stars) and Diagnosing Superpowers Sessions (obra/superpowers, 297k 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 Conversation?

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.