Agent skill

Fetch PR Comments

Fetch and summarize review feedback and conversation from a GitHub PR (unresolved review threads, review bodies, and PR conversation comments) without making changes.

MITAuto-check passed

Install Fetch PR Comments

skills CLI

$ npx skills add tobihagemann/turbo --skill fetch-pr-comments -a claude-code

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

GitHub CLI

$ gh skill install tobihagemann/turbo fetch-pr-comments --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/fetch-pr-comments .claude/skills/fetch-pr-comments && 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/

Paste into Claude Code

Install the "fetch-pr-comments" agent skill from https://github.com/tobihagemann/turbo/tree/main/codex/skills/fetch-pr-comments into .claude/skills/fetch-pr-comments/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "fetch-pr-comments", 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

$skill-installer install https://github.com/tobihagemann/turbo/tree/main/codex/skills/fetch-pr-comments

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

skills CLI

$ npx skills add tobihagemann/turbo --skill fetch-pr-comments -a codex

Project install goes to .agents/skills/; add -g for ~/.codex/skills/.

GitHub CLI

$ gh skill install tobihagemann/turbo fetch-pr-comments --agent codex

Project scope by default (.agents/skills/); add --scope user for a personal install.

Manual copy

$ git clone --depth 1 https://github.com/tobihagemann/turbo.git skills-src && mkdir -p .agents/skills && cp -r skills-src/codex/skills/fetch-pr-comments .agents/skills/fetch-pr-comments && rm -rf skills-src

Use ~/.agents/skills/ instead of .agents/skills for a personal install.

Codex skills documentation · loads skills from .agents/skills/

Paste into Codex

Install the "fetch-pr-comments" agent skill from https://github.com/tobihagemann/turbo/tree/main/codex/skills/fetch-pr-comments into .agents/skills/fetch-pr-comments/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "fetch-pr-comments", 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.

skills CLI

$ npx skills add tobihagemann/turbo --skill fetch-pr-comments -a cursor

Project install goes to .agents/skills/; add -g for ~/.cursor/skills/.

GitHub CLI

$ gh skill install tobihagemann/turbo fetch-pr-comments --agent cursor

Project scope by default (.agents/skills/); add --scope user for a personal install.

Manual copy

$ git clone --depth 1 https://github.com/tobihagemann/turbo.git skills-src && mkdir -p .cursor/skills && cp -r skills-src/codex/skills/fetch-pr-comments .cursor/skills/fetch-pr-comments && rm -rf skills-src

Use ~/.cursor/skills/ instead of .cursor/skills for a personal install.

Cursor skills documentation · loads skills from .cursor/skills/, .agents/skills/, .claude/skills/, .codex/skills/

Paste into Cursor

Install the "fetch-pr-comments" agent skill from https://github.com/tobihagemann/turbo/tree/main/codex/skills/fetch-pr-comments into .cursor/skills/fetch-pr-comments/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "fetch-pr-comments", 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

$ gemini skills install https://github.com/tobihagemann/turbo.git --path codex/skills/fetch-pr-comments

--scope user (default) or --scope workspace; --path is the subfolder of the repo that holds the skill; --consent skips the security confirmation prompt.

skills CLI

$ npx skills add tobihagemann/turbo --skill fetch-pr-comments -a gemini-cli

Project install goes to .agents/skills/; add -g for ~/.gemini/skills/.

GitHub CLI

$ gh skill install tobihagemann/turbo fetch-pr-comments --agent gemini-cli

Project scope by default (.agents/skills/); add --scope user for a personal install.

Manual copy

$ git clone --depth 1 https://github.com/tobihagemann/turbo.git skills-src && mkdir -p .gemini/skills && cp -r skills-src/codex/skills/fetch-pr-comments .gemini/skills/fetch-pr-comments && rm -rf skills-src

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

Paste into Gemini CLI

Install the "fetch-pr-comments" agent skill from https://github.com/tobihagemann/turbo/tree/main/codex/skills/fetch-pr-comments into .gemini/skills/fetch-pr-comments/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "fetch-pr-comments", 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.

GitHub CLI

$ gh skill install tobihagemann/turbo fetch-pr-comments

Installs 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).

skills CLI

$ npx skills add tobihagemann/turbo --skill fetch-pr-comments -a github-copilot

Project install goes to .agents/skills/; add -g for ~/.copilot/skills/.

Manual copy

$ git clone --depth 1 https://github.com/tobihagemann/turbo.git skills-src && mkdir -p .github/skills && cp -r skills-src/codex/skills/fetch-pr-comments .github/skills/fetch-pr-comments && rm -rf skills-src

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

Paste into GitHub Copilot

Install the "fetch-pr-comments" agent skill from https://github.com/tobihagemann/turbo/tree/main/codex/skills/fetch-pr-comments into .github/skills/fetch-pr-comments/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "fetch-pr-comments", 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.

skills CLI

$ npx skills add tobihagemann/turbo --skill fetch-pr-comments -a opencode

OpenCode documents no install command of its own. Project install goes to .agents/skills/; add -g for ~/.config/opencode/skills/.

GitHub CLI

$ gh skill install tobihagemann/turbo fetch-pr-comments --agent opencode

Project scope by default (.agents/skills/); add --scope user for a personal install.

Manual copy

$ git clone --depth 1 https://github.com/tobihagemann/turbo.git skills-src && mkdir -p .opencode/skills && cp -r skills-src/codex/skills/fetch-pr-comments .opencode/skills/fetch-pr-comments && rm -rf skills-src

Use ~/.config/opencode/skills/ instead of .opencode/skills for a personal install.

OpenCode skills documentation · loads skills from .opencode/skills/, .claude/skills/, .agents/skills/

Paste into OpenCode

Install the "fetch-pr-comments" agent skill from https://github.com/tobihagemann/turbo/tree/main/codex/skills/fetch-pr-comments into .opencode/skills/fetch-pr-comments/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "fetch-pr-comments", 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: fetch-pr-comments
GitHub stars: 407
Used in: 1 other repo
Token cost: ~967 tokens
SKILL.md length: 361 words
Files: 2 (incl. scripts)
Skills in repo: 81
Repo updated: Oct 7, 2026
First seen: Oct 7, 2026
Licence: MIT

At a glance

Fetch and summarize review feedback and conversation from a GitHub PR (unresolved review threads, review bodies, and PR conversation comments) without making changes.

Works in 2 steps: Fetch Comments → Present Results
The user asks to fetch PR comments
SKILL.md covers Step 1: Fetch Comments, Step 2: Present Results and Rules
Runs Shell scripts from its folder; calls bash

What it does

Fetch PR Comments is an agent skill from 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. Use when the user asks to "fetch PR comments", "show PR comments", "check PR for unresolved comments", "list review comments", "what comments are on the PR", "show unresolved threads", or "summarize PR feedback".

Its SKILL.md is about 970 tokens, which your agent loads only when the skill is triggered. The skill folder holds 2 other files, including scripts (for example `scripts/fetch-pr-data.sh`).

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 fetch PR comments
Show PR comments
Check PR for unresolved comments
List review comments

Example prompts

“fetch PR comments”
“show PR comments”
“check PR for unresolved comments”
“/fetch-pr-comments”

Requirements

A Bash shell

Workflow steps

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

Fetch Comments
Present Results

What it can do on your machine

Read from SKILL.md and the folder at commit 4b9f4cf. 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
Ships 1 file in scripts/ (Shell), which the agent can run.
Shell commands in SKILL.md call:
- bash
From the folder's file list and the shell code blocks in SKILL.md.
Network
No URLs in SKILL.md.
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

Fetch PR Comments loads about 967 tokens when it runs. Until then it costs about 99 tokens; SKILL.md has 361 words of instructions outside code blocks.

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

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); the scripts in this folder are not scanned.

SKILL.md

The full file from tobihagemann/turbo at commit 4b9f4cf, republished under its MIT licence (© tobihagemann). 361 words, ~967 tokens.

Download SKILL.mdSave it as .claude/skills/fetch-pr-comments/SKILL.md (or your agent's skills folder). This skill also uses 1 other file; get the full folder from GitHub.

name: fetch-pr-comments
description: Fetch and summarize review feedback and conversation from a GitHub PR (unresolved review threads, review bodies, and PR conversation comments) without making changes. Use when the user asks to "fetch PR comments", "show PR comments", "check PR for unresolved comments", "list review comments", "what comments are on the PR", "show unresolved threads", or "summarize PR feedback".

Fetch PR Comments

Fetch unresolved review comments, top-level review body comments, and PR conversation comments from a GitHub PR and present them in a readable summary. This is a read-only skill -- it does not evaluate, fix, or reply to any comments.

Step 1: Fetch Comments

Auto-detect owner, repo, and PR number from current branch if not provided. Then run scripts/fetch-pr-data.sh, which handles full pagination (review threads, inner comment pages for long threads, reviews, issue comments) and emits a single merged JSON document:

bash

bash <skill-dir>/scripts/fetch-pr-data.sh <owner> <repo> <pr_number>

Output shape:

jsonc

{
  "meta":          { "title", "url", "headRefName", "baseRefName" },
  "reviewThreads": [ { "id", "isResolved", "isOutdated", "comments": { "nodes": [ { "author", "body", "path", "line", "originalLine", "diffHunk" } ] } } ],
  "reviews":       [ { "author", "body", "state" } ],
  "issueComments": [ { "author", "body", "createdAt", "url" } ]
}

Filter review threads to unresolved only. Filter reviews to those with a non-empty body, excluding PENDING state (unsubmitted drafts). Filter issue comments to those with a non-empty body.

Step 2: Present Results

Display a summary header followed by comments grouped by file.

Summary header:

PR title and link
Branch: head -> base
Total threads / unresolved threads

Top-level review comments (if any):

Show reviews with non-empty body before the file-grouped threads:

## Review Comments

### @reviewer (CHANGES_REQUESTED)
> Review body text here

### @another-reviewer (COMMENTED)
> Another review body here

Issue comments (if any):

Show PR conversation comments after review comments, ordered by createdAt:

## Issue Comments

### @commenter (2026-04-20)
> Issue comment body here

### @another-commenter (2026-04-21)
> Another issue comment body here

Inline threads grouped by file:

For each file with unresolved threads, show:

## `path/to/file.ts`

### Line 42 (by @reviewer)
```diff
<diffHunk from first comment>
```
> Comment body here

### Line 10 (by @another-reviewer) [outdated]
```diff
<diffHunk from first comment>
```
> First comment body
>
> **@reply-author:** Reply body

Formatting rules:

Show top-level review body comments first, grouped under "Review Comments"
Show PR conversation comments next, grouped under "Issue Comments", ordered by createdAt
Then group threads by file path, in the order they appear
Within each file, order threads by line number
Show the diffHunk from the first comment in each thread as a fenced diff code block before the comment body. This is the code context the reviewer was looking at.
For the line number, use line if available. Fall back to originalLine for outdated comments where line is null.
Show all comments in a thread (the first is the original review comment; subsequent ones are replies)
Mark outdated threads with [outdated]
Use blockquotes for comment bodies
For threads with multiple comments, show each comment with its author
If there are zero unresolved threads, zero review body comments, and zero issue comments, say so and stop

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

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

Rules

If the user wants to fix or reply to comments, direct them to use $resolve-pr-comments.

Files

SKILL.md and 1 other file (scripts) in codex/skills/fetch-pr-comments of tobihagemann/turbo.

SKILL.md
scripts/fetch-pr-data.sh

Open the folder on GitHubat commit 4b9f4cf

Used in 1 other repository

We found 3 copies of this SKILL.md (exact, near-identical or edited) in other folders, from 1 other GitHub owner. This page covers the copy in tobihagemann/turbo, which our catalogue first saw on October 7, 2026.

majiayu000/claude-skill-registryskills/analysis/fetch-pr-comments skills/analysis/fetch-pr-comments-tobihagemann-turbo

Compare with similar skills

Fetch PR Comments 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.

Fetch PR Comments compared with similar skills
Skill	Stars	Used in	Tokens	Auto-check	Licence	Repo updated
Fetch PR Comments this skilltobihagemann/turbo	407	1 repos	~967	Automated safety check: Pass	MIT	yesterday
PR Babysitteropeninterpreter/openinterpreter	69k	3 repos	~4.2k	Automated safety check: Pass	Apache-2.0	2 days ago
Diagnosing Superpowers Sessionsobra/superpowers	296k	3 repos	~1.7k	Automated safety check: Pass	MIT	yesterday
GitHub Deep Researchbytedance/deer-flow	83k	5 repos	~1.3k	Automated safety check: Pass	MIT	yesterday
Greplooponyx-dot-app/onyx	32k	4 repos	~3.3k	Automated safety check: Pass	MIT	yesterday
Update V8 Versionopeninterpreter/openinterpreter	69k	2 repos	~845	Automated safety check: Pass	Apache-2.0	2 days ago

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
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.
296k GitHub starsUsed in 3 repos~1.7k tokens
Agent WorkflowsAuto-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.
83k GitHub starsUsed in 5 repos~1.3k tokens
Research & ScienceAuto-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
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.8k tokensUpdated yesterday
Research & ScienceAuto-check: notes

Questions about Fetch PR Comments

What does Fetch PR Comments do?

Fetch and summarize review feedback and conversation from a GitHub PR (unresolved review threads, review bodies, and PR conversation comments) without making changes. Fetch PR Comments is an agent skill from 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.

When should I use Fetch PR Comments?

Fetch PR Comments fits situations like: the user asks to fetch PR comments; show PR comments; check PR for unresolved comments; list review comments.

How do I install Fetch PR Comments in Claude Code?

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

How do I install Fetch PR Comments in Codex?

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

Can I use Fetch PR Comments 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 fetch-pr-comments -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/fetch-pr-comments, .gemini/skills/fetch-pr-comments, .github/skills/fetch-pr-comments and .opencode/skills/fetch-pr-comments in your project.

What does Fetch PR Comments need to run?

Going by SKILL.md and its folder, Fetch PR Comments needs a shell for the scripts in its folder and the command-line tools its instructions call (bash). Our summary lists: A Bash shell.

Does Fetch PR Comments access the network?

SKILL.md contains no URLs. Any network use would come from the scripts or tools the agent runs. This is read from the text; nothing was executed.

Is Fetch PR Comments 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. The check reads SKILL.md only: the scripts in the folder are not scanned, so read them before running anything.

What licence does Fetch PR Comments use?

Fetch PR Comments 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 Fetch PR Comments use?

About 967 tokens (SKILL.md is roughly 3.9k 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 Fetch PR Comments?

Skills that share tags, products or a category with Fetch PR Comments: PR Babysitter (openinterpreter/openinterpreter, 69k stars), Diagnosing Superpowers Sessions (obra/superpowers, 296k stars), GitHub Deep Research (bytedance/deer-flow, 83k stars) and Greploop (onyx-dot-app/onyx, 32k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.

Who maintains Fetch PR Comments?

tobihagemann (a GitHub user) maintains it in tobihagemann/turbo, which has 407 GitHub stars. The repository holds 81 skills in this directory. The repository was last updated on October 7, 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.

Fetch PR Comments

Install Fetch PR Comments

Facts

At a glance

What it does

When your agent uses it

Example prompts

Requirements

Workflow steps

What it can do on your machine

Tool permissions

Runs code

Network

Credentials

Context cost

Safety

SKILL.md

Fetch PR Comments

Step 1: Fetch Comments

Step 2: Present Results

Rules

Files

Used in 1 other repository

Compare with similar skills

Similar skills

PR Babysitter

Diagnosing Superpowers Sessions

GitHub Deep Research

Greploop

Update V8 Version

Last30days

More from tobihagemann/turbo

Consult Oracle

Recall Rationale

Codex Exec

Resolve PR Comments

Investigate

Resolve PR Comments

Questions about Fetch PR Comments

Install Fetch PR Comments

Facts

At a glance

What it does

When your agent uses it

Example prompts

Requirements

Workflow steps

What it can do on your machine

Tool permissions

Runs code

Network

Credentials

Context cost

Safety

SKILL.md

Fetch PR Comments

Step 1: Fetch Comments

Step 2: Present Results

Rules

Files

Used in 1 other repository

Compare with similar skills

Similar skills

More from tobihagemann/turbo

Related

Questions about Fetch PR Comments