PR Review State Fetch
prisma/orm
Fetches a pull request's canonical review state as JSON, validates it, and renders markdown, a text summary and triage target files from it using bundled scripts.
Pulls every review comment from the current branch's GitHub pull request into Warp's code review panel, then waits for your direction.
Install PR Review Comments Fetcher
$ npx skills add warpdotdev/warp --skill pr-comments -a claude-codeProject install by default; add -g for ~/.claude/skills/.
$ gh skill install warpdotdev/warp pr-comments --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/warpdotdev/warp.git skills-src && mkdir -p .claude/skills && cp -r skills-src/resources/bundled/skills/pr-comments .claude/skills/pr-comments && 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 "pr-comments" agent skill from https://github.com/warpdotdev/warp/tree/master/resources/bundled/skills/pr-comments into .claude/skills/pr-comments/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "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 install https://github.com/warpdotdev/warp/tree/master/resources/bundled/skills/pr-commentsType 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 warpdotdev/warp --skill pr-comments -a codexProject install goes to .agents/skills/; add -g for ~/.codex/skills/.
$ gh skill install warpdotdev/warp pr-comments --agent codexProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/warpdotdev/warp.git skills-src && mkdir -p .agents/skills && cp -r skills-src/resources/bundled/skills/pr-comments .agents/skills/pr-comments && rm -rf skills-srcUse ~/.agents/skills/ instead of .agents/skills for a personal install.
Codex skills documentation · loads skills from .agents/skills/
Install the "pr-comments" agent skill from https://github.com/warpdotdev/warp/tree/master/resources/bundled/skills/pr-comments into .agents/skills/pr-comments/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "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.
$ npx skills add warpdotdev/warp --skill pr-comments -a cursorProject install goes to .agents/skills/; add -g for ~/.cursor/skills/.
$ gh skill install warpdotdev/warp pr-comments --agent cursorProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/warpdotdev/warp.git skills-src && mkdir -p .cursor/skills && cp -r skills-src/resources/bundled/skills/pr-comments .cursor/skills/pr-comments && 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 "pr-comments" agent skill from https://github.com/warpdotdev/warp/tree/master/resources/bundled/skills/pr-comments into .cursor/skills/pr-comments/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "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 https://github.com/warpdotdev/warp.git --path resources/bundled/skills/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.
$ npx skills add warpdotdev/warp --skill pr-comments -a gemini-cliProject install goes to .agents/skills/; add -g for ~/.gemini/skills/.
$ gh skill install warpdotdev/warp pr-comments --agent gemini-cliProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/warpdotdev/warp.git skills-src && mkdir -p .gemini/skills && cp -r skills-src/resources/bundled/skills/pr-comments .gemini/skills/pr-comments && 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 "pr-comments" agent skill from https://github.com/warpdotdev/warp/tree/master/resources/bundled/skills/pr-comments into .gemini/skills/pr-comments/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "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.
$ gh skill install warpdotdev/warp pr-commentsInstalls 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 warpdotdev/warp --skill pr-comments -a github-copilotProject install goes to .agents/skills/; add -g for ~/.copilot/skills/.
$ git clone --depth 1 https://github.com/warpdotdev/warp.git skills-src && mkdir -p .github/skills && cp -r skills-src/resources/bundled/skills/pr-comments .github/skills/pr-comments && 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 "pr-comments" agent skill from https://github.com/warpdotdev/warp/tree/master/resources/bundled/skills/pr-comments into .github/skills/pr-comments/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "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.
$ npx skills add warpdotdev/warp --skill pr-comments -a opencodeOpenCode documents no install command of its own. Project install goes to .agents/skills/; add -g for ~/.config/opencode/skills/.
$ gh skill install warpdotdev/warp pr-comments --agent opencodeProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/warpdotdev/warp.git skills-src && mkdir -p .opencode/skills && cp -r skills-src/resources/bundled/skills/pr-comments .opencode/skills/pr-comments && 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 "pr-comments" agent skill from https://github.com/warpdotdev/warp/tree/master/resources/bundled/skills/pr-comments into .opencode/skills/pr-comments/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "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
pr-comments- GitHub stars
- 65k
- Used in
- 1 other repo
- Token cost
- ~1.1k tokens
- SKILL.md length
- 492 words
- Files
- 5 (incl. scripts)
- Skills in repo
- 46
- Repo updated
- First seen
- Licence
- AGPL-3.0
At a glance
Pulls every review comment from the current branch's GitHub pull request into Warp's code review panel, then waits for your direction.
- Works in 3 steps: Run the bundled script (must be inside a… → Call insert_code_review_comments with… → Stop and wait for the user. After…
- Reading all review comments on the PR for the current branch
- SKILL.md covers Procedure, What the Script Handles, Script fallback commands and Requirements
- Runs Python scripts from its folder; calls gh and python3; reaches github.com
What it does
A bundled Python script uses gh api with pagination to collect issue comments, inline diff comments and reviews for the open PR on the current branch, trims large diff hunks to a window around the commented line, and prints JSON. Reply comments get reply metadata and top-level diff comments get location metadata with file path, trimmed hunk, line and side, while PR-level comments carry neither. The agent passes the repository path, base branch and comments to insert_code_review_comments.
The role is purely informational. After showing each batch, the agent must ask how you want to proceed and take no action until told: no code changes in response to the comments and no review replies submitted in your name. If the script fails, fallback gh commands are given, including resolving the owner and repo from the PR's base repository so that forks do not cause 404 errors.
When your agent uses it
- Reading all review comments on the PR for the current branch
- Collecting reviewer feedback before deciding what to change
- Looking at review comments on a PR opened from a fork
Example prompts
- “Show me the review comments on my current PR.”
- “Pull the reviewer feedback for this branch so I can decide which comments to address.”
- “Fetch the PR comments but do not change any code yet.”
Requirements
- Python 3 and the GitHub CLI (gh)
- A git repository with an open PR on the current branch
Workflow steps
3 steps, taken from the first numbered list in SKILL.md.
- Run the bundled script (must be inside a git repo with an open PR on the current branch).
- Call insert_code_review_comments with the three top-level fields from the JSON output
- Stop and wait for the user. After displaying each batch of comments, you MUST ask the user how they would like to proceed. Do NOT take any…
What it can do on your machine
Read from SKILL.md and the folder at commit f571865. 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 4 files in scripts/ (Python), which the agent can run.
Shell commands in SKILL.md call:
ghpython3
From the folder's file list and the shell code blocks in SKILL.md.
Network
Hosts in commands or code, which the agent is likely to contact:
github.com
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
PR Review Comments Fetcher loads about 1.1k tokens when it runs. Until then it costs about 20 tokens; SKILL.md has 492 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); the scripts in this folder are not scanned.
SKILL.md
The full file from warpdotdev/warp at commit f571865, republished under its AGPL-3.0 licence (© warpdotdev). 492 words, ~1,113 tokens.
Download SKILL.mdSave it as
.claude/skills/pr-comments/SKILL.md (or your agent's skills folder). This skill also uses 4 other files; get the full folder from GitHub.- name
- pr-comments
- description
- Fetch and display GitHub PR review comments for the current branch.
Fetch PR Comments
Fetch all review comments from the current branch's GitHub PR and display them via insert_code_review_comments.
Procedure
Run the bundled script (must be inside a git repo with an open PR on the current branch). Use
do_not_summarize_output: truewhen running this shell command so the JSON output is not truncated.bash python3 {{skill_dir}}/scripts/fetch_github_review_comments.pyThe script prints JSON to stdout. If the script fails to fetch comments, run the fallback
ghcommands instead.Call
insert_code_review_commentswith the three top-level fields from the JSON output:local_repository_pathbase_branchcomments
Stop and wait for the user. After displaying each batch of comments, you MUST ask the user how they would like to proceed. Do NOT take any further action until the user provides explicit instructions unless the user explicitly asks you to. Do NOT make code changes in response to the fetched comments unless the user tells you to. Do NOT impersonate the user by submitting review responses. Your role when fetching and displaying comments is purely informational — present the comments and wait for direction.
What the Script Handles
- Fetches issue comments, diff comments, and reviews via
gh api --paginate - Trims large diff hunks to a window around the commented line
- Sets
reply_metadataon reply comments - Sets
location_metadataon top-level diff comments (filepath, trimmed diff hunk, line, side) - PR-level comments (issue comments and reviews) have neither location nor reply metadata
Show full SKILL.md (264 more words)Show less
Script fallback commands
If the script fails to fetch comments, follow these steps to fetch comments directly from the GitHub API:
Use the GitHub cli to find the PR number and PR base branch for the current branch. Determine
{owner_login}/{repo_name}from the base repository (the repo that owns the PR) by parsing the PR'surl(e.g.https://github.com/{owner_login}/{repo_name}/pull/{pr_number}). Comments live on the base repo, so this resolves correctly even when the PR was opened from a fork — do not use the head/fork repository or the endpoints will 404.Use the GitHub /repos/{owner_login}/{repo_name}/issues/{pr_number}/comments endpoint to fetch PR-level comments.
Use the GitHub /repos/{owner_login}/{repo_name}/pulls/{pr_number}/comments endpoint to fetch line- and file-attached review comments. Remove location metadata and diff hunks from thread replies.
Use the GitHub /repos/{owner_login}/{repo_name}/pulls/{pr_number}/reviews endpoint with a filter to fetch code reviews with comment text.
Invoke the
insert_code_review_commentstool to send the comments to the user. Include all PR-, review-, file- and line-level comments. If there are no comments on the PR, use the tool to return an empty list. DO NOT read out the comment contents without the tool.
Ensure the pager is not used by clearing the GH_PAGER environment variable. For example, on MacOS using zsh, use:
$ GH_PAGER="" gh pr view --json number,url,baseRefName
$ GH_PAGER="" gh api /repos/{owner_login}/{repo_name}/issues/{pr_number}/comments --jq '.[] | {id, html_url, user_login: .user.login, body, created_at, updated_at}'
$ GH_PAGER="" gh api /repos/{owner_login}/{repo_name}/pulls/{pr_number}/comments --jq '.[] | {id, html_url, diff_hunk, path, user_login: .user.login, body, created_at, updated_at, start_line, original_start_line, start_side, line, original_line, side, in_reply_to_id, subject_type} | if .in_reply_to_id != null then del(.diff_hunk, .path, .line, .original_line, .start_line, .original_start_line, .side, .start_side, .subject_type) else . end'
$ GH_PAGER="" gh api /repos/{owner_login}/{repo_name}/pulls/{pr_number}/reviews --jq '.[] | {id, html_url, user_login: .user.login, body, created_at, updated_at} | select(.body != "" and .body != null)'Adapt the instructions above for the user's operating system and shell. Then invoke the insert_code_review_comments tool.
- After displaying comments, follow step 3 of the Procedure above: stop and ask the user how they want to proceed. Do NOT take any action on the comments without explicit user direction.
Requirements
ghCLI authenticated with repo access- Current branch has an open pull request
© warpdotdev, AGPL-3.0. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file
Files
SKILL.md and 4 other files (scripts) in resources/bundled/skills/pr-comments of warpdotdev/warp.
- SKILL.md
- scripts/fetch_github_review_comments.py
- scripts/test_fetch_comments.py
- scripts/test_trim_diff_hunk.py
- scripts/trim_diff_hunk.py
Open the folder on GitHubat commit f571865
Used in 1 other repository
We found 1 copy of this SKILL.md (exact, near-identical or edited) in other folders, from 1 other GitHub owner. This page covers the copy in warpdotdev/warp, which our catalogue first saw on October 7, 2026.
Compare with similar skills
PR Review Comments Fetcher 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 |
|---|---|---|---|---|---|---|
| PR Review Comments Fetcher this skillwarpdotdev/warp | 65k | 1 repos | ~1.1k | Automated safety check: Pass | AGPL-3.0 | |
| PR Review State Fetchprisma/orm | 48k | — | ~767 | Automated safety check: Pass | Apache-2.0 | |
| Greploop Appsmichaelshimeles/skills | 1.3k | 1 repos | ~3.6k | Automated safety check: Pass | MIT | |
| PR Triagertk-ai/rtk | 83k | — | ~2.5k | Automated safety check: Notes | Apache-2.0 | |
| GitHub Fork and PR Submissionjxxghp/MoviePilot | 12k | — | ~1.1k | Automated safety check: Notes | GPL-3.0 | |
| Difit Reviewyoshiko-pg/difit | 3.2k | — | ~1.2k | Automated safety check: Pass | MIT |
Similar skills
- Official
Greploop Apps
michaelshimeles/skills
Loops on a large pull request, merge request or Perforce changelist, fixing Greptile findings until it scores 5/5 with no unresolved comments.
PR Triage
rtk-ai/rtk
Audits a repository's open pull requests, deep-reviews chosen ones and drafts review comments that are only posted after you approve them.
GitHub Fork and PR Submission
jxxghp/MoviePilot
Submits code changes as a GitHub pull request through an isolated Git clone, reusing or creating your fork and pushing only after you confirm the real diff.
Difit Review
yoshiko-pg/difit
Review a specific diff (branch, commit, or GitHub PR) and show the findings as comments inside difit, the local diff viewer.
Address PR Feedback for ruby-git
ruby-git/ruby-git
Addresses unresolved pull request review threads and suppressed (low-confidence) Copilot review comments on the current branch, folds each fix into the…
More from warpdotdev/warp
All 46 skills in this repoFigma Design System Builder
warpdotdev/warp
Builds or updates a design system in Figma from a codebase in ordered phases: discovery, variables and tokens, components, theming and documentation, with checkpoints.
Figma use_figma Plugin API Rules
warpdotdev/warp
Required groundwork before any use_figma call: the rules and reference files for running JavaScript in a Figma file through the Plugin API without common failures.
Warp Factory Files
warpdotdev/warp
Authors and edits file-based Warp software factory definitions rooted at factory.yaml, covering agents, automations, scorers and webhooks, and validates them before a pull request.
Figma Design to Code
warpdotdev/warp
Turns a Figma frame or component into production code that matches the design, using the Figma MCP server and the project's own design system.
Warp GUI to Agent CLI Migration
warpdotdev/warp
Migrates the compatible subset of settings and global file-based MCP servers from the Warp desktop app into Warp Agent CLI without exposing credentials or state.
Figma Design System Rules Generator
warpdotdev/warp
Creates project-specific design system rules from your codebase so coding agents implement Figma designs with your components, naming and tokens.
Related
Categories
Questions about PR Review Comments Fetcher
What does PR Review Comments Fetcher do?
Pulls every review comment from the current branch's GitHub pull request into Warp's code review panel, then waits for your direction. A bundled Python script uses gh api with pagination to collect issue comments, inline diff comments and reviews for the open PR on the current branch, trims large diff hunks to a window around the commented line, and prints JSON. Reply comments get reply metadata and top-level diff comments get location metadata with file path, trimmed hunk, line and side, while PR-level comments carry neither.
When should I use PR Review Comments Fetcher?
PR Review Comments Fetcher fits situations like: reading all review comments on the PR for the current branch; collecting reviewer feedback before deciding what to change; looking at review comments on a PR opened from a fork.
How do I install PR Review Comments Fetcher in Claude Code?
Run `npx skills add warpdotdev/warp --skill pr-comments -a claude-code`. Or copy the skill folder (resources/bundled/skills/pr-comments in warpdotdev/warp) into .claude/skills/pr-comments in your project. Claude Code loads it when a task matches its description.
How do I install PR Review Comments Fetcher in Codex?
Run `npx skills add warpdotdev/warp --skill pr-comments -a codex`. Or copy the skill folder (resources/bundled/skills/pr-comments in warpdotdev/warp) into .agents/skills/pr-comments in your project. Codex loads it when a task matches its description.
Can I use PR Review Comments Fetcher 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 warpdotdev/warp --skill 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/pr-comments, .gemini/skills/pr-comments, .github/skills/pr-comments and .opencode/skills/pr-comments in your project.
What does PR Review Comments Fetcher need to run?
Going by SKILL.md and its folder, PR Review Comments Fetcher needs Python for the scripts in its folder and the command-line tools its instructions call (gh and python3). Our summary lists: Python 3 and the GitHub CLI (gh); A git repository with an open PR on the current branch.
Does PR Review Comments Fetcher access the network?
SKILL.md names 1 domain. In commands or code: github.com; the agent is likely to contact it when it follows the instructions. This is read from the text; nothing was executed.
Is PR Review Comments Fetcher 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 PR Review Comments Fetcher use?
PR Review Comments Fetcher is published under the AGPL-3.0 licence (the repository's licence). It allows redistribution, so the full SKILL.md is shown on this page.
How many tokens does PR Review Comments Fetcher use?
About 1.1k tokens (SKILL.md is roughly 4.5k 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 PR Review Comments Fetcher?
Skills that share tags, products or a category with PR Review Comments Fetcher: PR Review State Fetch (prisma/orm, 48k stars), Greploop Apps (michaelshimeles/skills, 1.3k stars), PR Triage (rtk-ai/rtk, 83k stars) and GitHub Fork and PR Submission (jxxghp/MoviePilot, 12k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.
Who maintains PR Review Comments Fetcher?
warpdotdev (a GitHub organization) maintains it in warpdotdev/warp, which has 65,380 GitHub stars. The repository holds 46 skills in this directory. The repository was last updated on October 7, 2026.
Source: warpdotdev/warp on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.