Address GitHub PR comments

Fetches all comments, reviews and inline threads on the current branch's GitHub PR with a gh GraphQL script, numbers them and fixes only the ones you pick. Use when a PR has review comments to work through and you want to choose which get changed.

Git & PRsPack: OpenAI skills25 linesgh-address-comments
Author
Source
openai/skills/skills/.curated/gh-address-comments @ 49f948f
License
Apache-2.0

About this skill

What it does

The skill helps the agent work through the comments on the open pull request for the current branch, with you choosing which ones to act on: check that gh is logged in, fetch every comment, list them, ask, fix.

The fetching is done by scripts/fetch_comments.py. It finds the PR that gh pr view links to the branch, then runs one GraphQL query through gh api graphql and pages through three lists: conversation comments, review submissions with their state (approved, changes requested, commented), and inline review threads with file path, line and the resolved and outdated flags. It prints one JSON document and needs only Python and gh.

The agent then numbers every thread and comment, writes a one-line summary of what a fix would take for each, and asks which numbers to address. Only the chosen ones get changed. The skill does not reply on GitHub, resolve threads, commit or push; those steps stay with you.

When to use it, and when not

Use it when a PR has collected review comments and you want them in one numbered list, choosing what the agent touches.

It always works on the PR of the checked-out branch, and it has no step for checking whether a comment is correct before fixing it.

How to run it

The install command below puts the whole folder in place: SKILL.md, the script, the icons, the Codex metadata file and the licence. You need the GitHub CLI logged in (gh auth login) with repo and workflow scopes. The notes about elevated network access and sandbox_permissions concern the Codex sandbox. To call it:

  • Claude Code: /gh-address-comments, or ask for the skill by name.
  • Codex: $gh-address-comments.
  • Cursor: type / in the Agent chat and pick gh-address-comments.

Example: /gh-address-comments List the open review threads on this branch's PR; I'll pick which to fix.

OpenAI has marked openai/skills deprecated; our copy is pinned to a commit there, and as of November 2026 openai/plugins has no newer version of this skill.

How it differs from similar skills

Responding to review feedback treats each comment as a claim to verify, fixes the correct ones, pushes back with evidence on the rest and drafts a reply per comment. Receiving code review sets the same verify-first attitude without tooling. Iterate a PR until CI is green sorts feedback into high, medium and low, fixes the first two on its own, replies to threads and loops with CI. This skill only collects and leaves the choice to you.

Install

Run one command — it saves SKILL.md and the files it uses into your agent's skills folder. Claude Code and Codex pick up a new skill without a restart; if it does not show up, restart the agent.

Claude Code — macOS, Linux
curl -fsSL --create-dirs -o ~/.claude/skills/gh-address-comments/SKILL.md https://anymodel.org/en/skills/openai/gh-address-comments/SKILL.md -o ~/.claude/skills/gh-address-comments/LICENSE.txt https://anymodel.org/en/skills/openai/gh-address-comments/LICENSE.txt -o ~/.claude/skills/gh-address-comments/agents/openai.yaml https://anymodel.org/en/skills/openai/gh-address-comments/agents/openai.yaml -o ~/.claude/skills/gh-address-comments/assets/github-small.svg https://anymodel.org/en/skills/openai/gh-address-comments/assets/github-small.svg -o ~/.claude/skills/gh-address-comments/assets/github.png https://anymodel.org/en/skills/openai/gh-address-comments/assets/github.png -o ~/.claude/skills/gh-address-comments/scripts/fetch_comments.py https://anymodel.org/en/skills/openai/gh-address-comments/scripts/fetch_comments.py
Codex, Cursor — macOS, Linux
curl -fsSL --create-dirs -o ~/.agents/skills/gh-address-comments/SKILL.md https://anymodel.org/en/skills/openai/gh-address-comments/SKILL.md -o ~/.agents/skills/gh-address-comments/LICENSE.txt https://anymodel.org/en/skills/openai/gh-address-comments/LICENSE.txt -o ~/.agents/skills/gh-address-comments/agents/openai.yaml https://anymodel.org/en/skills/openai/gh-address-comments/agents/openai.yaml -o ~/.agents/skills/gh-address-comments/assets/github-small.svg https://anymodel.org/en/skills/openai/gh-address-comments/assets/github-small.svg -o ~/.agents/skills/gh-address-comments/assets/github.png https://anymodel.org/en/skills/openai/gh-address-comments/assets/github.png -o ~/.agents/skills/gh-address-comments/scripts/fetch_comments.py https://anymodel.org/en/skills/openai/gh-address-comments/scripts/fetch_comments.py
Claude Code — Windows PowerShell
foreach ($f in 'SKILL.md','LICENSE.txt','agents/openai.yaml','assets/github-small.svg','assets/github.png','scripts/fetch_comments.py') { $p = Join-Path "$HOME\.claude\skills\gh-address-comments" $f; New-Item -ItemType Directory -Force (Split-Path $p) | Out-Null; Invoke-WebRequest "https://anymodel.org/en/skills/openai/gh-address-comments/$f" -UseBasicParsing -OutFile $p }
Codex, Cursor — Windows PowerShell
foreach ($f in 'SKILL.md','LICENSE.txt','agents/openai.yaml','assets/github-small.svg','assets/github.png','scripts/fetch_comments.py') { $p = Join-Path "$HOME\.agents\skills\gh-address-comments" $f; New-Item -ItemType Directory -Force (Split-Path $p) | Out-Null; Invoke-WebRequest "https://anymodel.org/en/skills/openai/gh-address-comments/$f" -UseBasicParsing -OutFile $p }

Any other agent: save the file into its skills folder, or give it the link to the file: https://anymodel.org/en/skills/openai/gh-address-comments/SKILL.md

SKILL.md

Raw

PR Comment Handler

Guide to find the open PR for the current branch and address its comments with gh CLI. Run all gh commands with elevated network access.

Prereq: ensure gh is authenticated (for example, run gh auth login once), then run gh auth status with escalated permissions (include workflow/repo scopes) so gh commands succeed. If sandboxing blocks gh auth status, rerun it with sandbox_permissions=require_escalated.

1) Inspect comments needing attention

  • Run scripts/fetch_comments.py which will print out all the comments and review threads on the PR

2) Ask the user for clarification

  • Number all the review threads and comments and provide a short summary of what would be required to apply a fix for it
  • Ask the user which numbered comments should be addressed

3) If user chooses comments

  • Apply fixes for the selected comments

Notes:

  • If gh hits auth/rate issues mid-run, prompt the user to re-authenticate with gh auth login, then retry.

Connect through AnyModel API

This skill runs on whatever model your agent uses. Point Claude Code, Codex or Cursor at AnyModel to run it on Claude, GPT, Gemini and more with one key — pay per token, no subscription.

More from the pack OpenAI skills

ASP.NET Core apps

Guides the agent through current ASP.NET Core practice: choosing Blazor, Razor Pages, MVC or Minimal APIs, Program.cs and middleware order, auth, EF Core, tests and upgrades to .NET 10. Use when building, reviewing or upgrading an ASP.NET Core app.

ChatGPT Apps SDK

Builds ChatGPT apps on the Apps SDK: reads current OpenAI docs first, picks an app archetype, plans MCP tools, adapts an official example or scaffolds a Node server and widget, then tests in Developer Mode. Use when building or fixing an app inside ChatGPT.

CLI creator from API docs

Builds a durable CLI from API docs, an OpenAPI spec, curls or a script: JSON output, doctor and dry-run commands, safe auth, installed on PATH and paired with a companion skill. Use when an agent keeps hitting the same service through ad hoc calls.

Define a measurable goal

Turns a fuzzy intention into one measurable goal with a validator, scope and stop condition, then registers it via get_goal and create_goal. Use before goal-backed or long-running agent work, when "done" needs a number or a check.

Fix failing GitHub Actions checks

Finds failing GitHub Actions checks on a PR with gh, pulls the logs, extracts the failure snippet and drafts a fix plan, changing code only after approval. Use when a PR's CI is red and you want the cause and a plan before any edit.

Jupyter notebooks

Creates and tidies Jupyter notebooks for experiments or tutorials from bundled templates via a stdlib script, with structure patterns and a run-top-to-bottom checklist. Use when starting a notebook or turning a messy one into something others can rerun.

Linear issues and projects

Works with Linear issues, projects and cycles through Linear's MCP server in a fixed order: setup, scope, read, then write, with sample workflows for triage, sprints and releases. Use when an agent should read or update Linear as part of a task.

Deploy to Netlify

Deploys the current project to Netlify with `npx netlify`: checks the login, links the folder to a site by Git remote or creates one, builds locally and returns a preview or production URL. Use when you want to publish a site to Netlify from your machine.

Browser automation with Playwright CLI

Drives a real browser from the terminal with playwright-cli: snapshots give element refs for clicks and typing, plus screenshots, console, network and traces, with no test files written. Use when a task needs a browser clicked through step by step.

Deploy to Render

Deploys an app to Render from a Git repo: writes and validates a render.yaml Blueprint with services, databases and secrets, or creates one service through the Render MCP server, then checks status and logs. Use when an app needs hosting on Render.

Security best-practice review

Checks Python, JavaScript/TypeScript and Go code against bundled security specs for ten frameworks, writes a report by severity with line numbers and fixes one finding at a time. Use when you explicitly ask for a security best-practice review.

Repository threat model

Writes a repository-grounded threat model: trust boundaries, assets, attacker capabilities and ranked abuse paths with mitigations, asking you to confirm key assumptions before the final file. Use when you explicitly ask to threat model a codebase.

Sentry issues and events

Reads Sentry issues and events through the sentry CLI without changing anything: recent production errors, issue and event details, AI root-cause summaries, with PII redacted. Use when you ask what is failing in production according to Sentry.

Deploy to Vercel

Deploys a project to Vercel, as a preview unless told otherwise, through the Vercel CLI or, without an account, a bundled script that uploads the folder and returns a preview link and a claim link. Use when you want a shareable deployment link fast.

Figma MCP design context

Reads Figma frames through the Figma MCP server in a fixed order (design context, metadata, screenshot) and rebuilds them with the project's components and tokens; also covers server setup in Codex. Use when connecting Figma MCP or coding from a frame link.

Figma use_figma prerequisite

Sets the rules an agent must load before every use_figma call that runs Plugin API JavaScript in a Figma file: return values, page resets, colours, fonts, node IDs, small validated steps. Use when creating or editing anything inside a Figma file.

Implement a Figma design in code

Implements a Figma frame or component as code in your repo with 1:1 visual parity: fetches context and a screenshot, maps the output to project tokens and components, then runs a validation checklist. Use when a Figma link must become production UI.

Generate a Figma design from an app

Builds or updates a full screen in Figma from code or a description, section by section, using the file's published components, variables and styles instead of hardcoded values. Use when a page from your app should exist as a Figma screen.

Figma design system from a codebase

Builds a Figma design system library from a codebase in five supervised phases: discovery, variables and styles, page structure, components one by one, QA. Use when a product needs a Figma library that matches its code tokens and components.

Figma Code Connect components

Links published Figma components to the code components that implement them via Code Connect: finds unmapped ones, matches them in the codebase, maps only what the user approves. Use when a Figma library and its code both exist but are not linked.

Figma design system rules

Writes project rules for turning Figma designs into code into CLAUDE.md, AGENTS.md or a Cursor rules file, based on Figma's rule template and an analysis of the codebase. Use when setting up an agent for regular Figma-to-code work in a repo.

Create a new Figma file

Creates a blank Figma design file or FigJam board in your drafts, resolving the plan through whoami, and returns the file key and URL. Use when the next Figma step needs a fresh file to write into.