mcpbeat

Gh Address Comments

openai/gh-address-comments

Help address review/issue comments on the open GitHub PR for the current branch using gh CLI; verify gh auth first and prompt the user to authenticate if not logged in.

This is a copy. The original lives at comeonoliver/gh-address-comments.

6k tokens
context cost
the whole folder, loaded on every use
6
files
ships runnable scripts
2
copies elsewhere
how many repositories repackaged it
24488
stars on the repo
on the repository, not the skill itself

Install

one command, takes just this skill from the repository 
npx skills add https://github.com/openai/skills --skill gh-address-comments

What comes with it

20 888 bytes besides the instruction
LICENSE.txt
agents/openai.yaml
assets/github-small.svg
assets/github.png
scripts/fetch_comments.py

The instruction itself

4 sections, as written by the author

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.

Repackaged in 2 other repositories

same content, different owner
ComeOnOliver/skillshub open on GitHub →

How to use it

Copy the folder

Take openai/gh-address-comments from the repository into ~/.claude/skills for personal use, or into .claude/skills inside a project.

Check the name does not clash

The agent identifies a skill by the name field in its header. Two skills with the same name cannot sit side by side — one of them will be ignored.