fetch-pr-comments SKILL.md skillA
fetch-pr-comments 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/fetch-pr-comments@git:20260721.ff8585dPins git:20260721.ff8585d in mdr.lock. Pin the fingerprint instead.
- Audit grade
- A, 17 of 17 checks passed
- Kind
- SKILL.md skill
- Repository
- tobihagemann/turbo
- Path
codex/skills/fetch-pr-comments/SKILL.md- Versions recorded
- 2
- Latest version
- git:20260721.ff8585d, committed Jul 21, 2026
- First version recorded
- May 8, 2026
- Size
- 3,868 bytes
- Repository stars
- 418
- License
- MIT
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".
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
# 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.
…Read the whole file at its exact version.
How to install
mdr add tobihagemann/turbo/fetch-pr-comments@sha256:3a1c0cf108b85d8bThe line at the top of this page pins the label git:20260721.ff8585d, 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_hjo5grvfossyvs52)
4 badge image fetches in 30 days. What the badge shows.
Versions
The registry has recorded 2 versions of this file, between May 8, 2026 and Jul 21, 2026, about one every 74 days.
| version | committed | commit | size | audit | |
|---|---|---|---|---|---|
| git:20260721.ff8585d latest | 2026-07-21 | ff8585d | 3,868 B | A | view · diff |
| git:20260508.4249183 | 2026-05-08 | 4249183 | 3,832 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 (3868 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_hjo5grvfossyvs52 GET https://markdownregistry.com/api/v1/resolve?ref=tobihagemann/turbo/fetch-pr-comments GET https://markdownregistry.com/api/v1/blob/3a1c0cf108b85d8b49b9df2e229345159afbbef84de0c26b3784d6f9514432a1
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