Menu
Fetch and display GitHub PR review comments for the current branch.
Instalar com Codex ou Claude Copie este prompt, cole no Codex, Claude ou outro assistente e deixe que ele revise a página da skill e instale para você.
Baseado na classificação ocupacional SOC
**MANDATORY prerequisite** — you MUST invoke this skill BEFORE every `use_figma` tool call. NEVER call `use_figma` directly without loading this skill first. Skipping it causes common, hard-to-debug failures. Trigger whenever the user wants to perform a write action or a unique read action that requires JavaScript execution in the Figma file context — e.g. create/edit/delete nodes, set up variables or tokens, build components and variants, modify auto-layout or fills, bind variables to properties, or inspect file structure programmatically.
Guides testing Warp UI features and changes using the computer use tool. Use this skill only when the computer_use tool is available to the agent. Covers launching Warp and verifying UI behavior.
Repo-specific review guidance for warp. Only the categories declared overridable by the core review-pr skill may be specialized here.
Control and inspect the currently running local Warp application with the warpctrl CLI. Use this skill whenever the user asks the agent to manipulate Warp's own windows, tabs, panes, sessions, input buffer, themes, or UI surfaces; open a file in Warp; inspect local Warp state; or explain how to invoke Warp Control manually.
Create new skills, modify and improve existing skills, and measure skill performance. Use when users want to create a skill from scratch, edit, or optimize an existing skill, run evals to test a skill, benchmark skill performance with variance analysis, or optimize a skill's description for better triggering accuracy.
View or modify Warp application settings using the bundled JSON schema for guidance
| name | pr-comments |
| description | Fetch and display GitHub PR review comments for the current branch. |
Fetch all review comments from the current branch's GitHub PR and display them via insert_code_review_comments.
Run the bundled script (must be inside a git repo with an open PR on the current branch).
Use do_not_summarize_output: true when running this shell command so the JSON output is not truncated.
python3 {{skill_dir}}/scripts/fetch_github_review_comments.py
The script prints JSON to stdout.
If the script fails to fetch comments, run the fallback gh commands instead.
Call insert_code_review_comments with the three top-level fields from the JSON output:
local_repository_pathbase_branchcommentsStop 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.
gh api --paginatereply_metadata on reply commentslocation_metadata on top-level diff comments (filepath, trimmed diff hunk, line, side)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's url (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_comments tool 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.
gh CLI authenticated with repo access