Index of every page on this site: llms.txt
All skills
openai avatar

/gh-address-comments

@49f948f official
by openaiopenai/skills29k stars
2,023
Run it yourself

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.

Use this Skill: https://skilld.dev/gh/openai/skills/gh-address-comments

Nothing lands on disk. Nothing to clean up.

Fork this Skill

Edit a local copy. It keeps the author and licence.

SKILL.md

≈47 tokens for metadata: the name and description. ≈248 when used: this file. ≈76 more on demand in 1 file.

Description uses 2.4% of example budget

Before choosing a Skill, your Agent reads its name and description. All available Skills share that space.

  • A shorter description leaves more room for other Skills. This entry exceeds our 1% size suggestion.

In our Claude Code example, all Skill names and descriptions share 8,000 characters. This Skill uses ≈190 characters, or 2.4%.

The 1% threshold is a size suggestion. Longer descriptions can still fit.

Your model, settings, and other Skills decide how much text your Agent can read.

Example settings and source

The example uses a 200k-token context and default Claude Code settings. The count includes the name, description, separators, and when_to_use when present. Codex also counts local file paths.

Skit's source and limits: Codex 0.160.1, Claude Code 2.1.292.

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.

Source: SKILL.md on GitHub

skilld matched fixed text patterns in SKILL.md and file names. Patterns miss obfuscated code.

skilld run checks every file with the same patterns. It asks for approval before it loads a Skill with a behavior marked Needs approval.

2 warnings2mo5 checks · Risk SAFE
  • Gen Agent Trust Hub2mo

    This skill includes some security considerations such as executing shell commands via the GitHub CLI and ingesting untrusted data from external pull request comments. While these warrant review, they are used within the skill's intended functionality to assist with code reviews.

  • Socket2mo

    No alerts

  • Snyk2mo

    Risk: MEDIUM · 1 issue

  • Runlayer9mo

    4/4 files flagged

  • ZeroLeaks7mo

    Score: 93/100 · 2 sections analyzed

Signed by skilld at 49f948f. This ties the file your Agent reads to that commit on GitHub. It does not review the instructions.

Last checked against GitHub last month.

Activeupdated last year
metadata
{
  "short-description": "Address comments in a GitHub PR review"
}
  • github
  • gh-cli
  • pull-requests
  • code-review
  • automation
  • workflow

README badge

README badge for openai/skills/gh-address-comments

Fetches review comments from the open GitHub PR for the current branch using gh CLI, displays them with summaries, and applies fixes for user-selected comments. Targets workflows where an AI agent needs to interactively address PR feedback without leaving the terminal.

Generated from the current SKILL.md.

Does this skill require GitHub CLI to be installed?
Yes. The skill uses gh CLI commands and assumes gh is already installed and authenticated on the system.
What happens if gh authentication fails?
The skill prompts you to re-authenticate with gh auth login and retry the operation.
Can this skill address comments on any branch, or only the current branch?
Only the current branch. The skill finds the open PR associated with the current Git branch and addresses comments on that PR.
Does this skill automatically apply fixes to comments, or does it ask first?
It lists all comments with a summary of what would be required to fix each one, then asks you which numbered comments to address before applying any fixes.

Generated from the current SKILL.md. These answers refresh after source changes.