openai/skills/skills/.curated/gh-address-comments/SKILL.md
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.
- Source repository stars
- 24,265
- Declared platforms
- 0
- Static risk flags
- 0
- Last source update
- 2026-07-14
- Source checked
- 2026-07-28
Decision brief
What it does—and where it fits
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.
Not for
- Tasks that require unconfirmed production actions or broad system permissions.
- Environments where the pinned source and install steps cannot be inspected.
Compatibility matrix
Platform support, with evidence labels
| Platform | Status | Evidence | What to check |
|---|---|---|---|
| Codex | Not declared | No explicit evidence | Portability before use |
| Claude Code | Not declared | No explicit evidence | Portability before use |
| Cursor | Not declared | No explicit evidence | Portability before use |
| Gemini CLI | Not declared | No explicit evidence | Portability before use |
Installation
Inspect first. Install second.
The source command is displayed only when detected. A safe inspection prompt is always available so your agent can explain every action before execution.
npx skills add https://github.com/openai/skills --skill "skills/.curated/gh-address-comments"Inspect the Agent Skill "gh-address-comments" from https://github.com/openai/skills/blob/49f948faa9258a0c61caceaf225e179651397431/skills/.curated/gh-address-comments/SKILL.md at commit 49f948faa9258a0c61caceaf225e179651397431. List every install step, command, network request, credential, file read/write, external action, and rollback step. Explain whether it fits my task. Do not install or execute anything until I approve.
Workflow
What the source asks the agent to do
- 01
1) Inspect comments needing attention
Run scripts/fetchcomments.py which will print out all the comments and review threads on the PR
Run scripts/fetchcomments.py which will print out all the comments and review threads on the PR- Run scripts/fetchcomments.py which will print out all the comments and review threads on the PR - 02
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
Number all the review threads and comments and provide a short summary of what would be required to apply a fix for itAsk the user which numbered comments should be addressed- 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 - 03
3) If user chooses comments
Notes: - If gh hits auth/rate issues mid-run, prompt the user to re-authenticate with gh auth login, then retry.
Apply fixes for the selected commentsIf gh hits auth/rate issues mid-run, prompt the user to re-authenticate with gh auth login, then retry.- Apply fixes for the selected comments
Permission review
Static risk signals and limitations
No configured static risk pattern was detected
This is not proof of safety. Runtime behavior, indirect dependencies, and hidden external systems are outside the static scan.
Evidence record
Why each signal appears
| Signal | Value | Evidence type | Meaning |
|---|---|---|---|
| Quality score | 59/100 | Computed | Documentation, specificity, maintenance, and trust rules |
| Repository stars | 24,265 | Source | Repository attention, not individual Skill quality |
| Compatibility | 0 platforms | Source | Declared in the catalog source record |
| Usage guide | catalog record | Editorial | Generated or reviewed according to the visible evidence level |
Pinned source
Provenance and original SKILL.md
- Repository
- openai/skills
- Skill path
- skills/.curated/gh-address-comments/SKILL.md
- Commit
- 49f948faa9258a0c61caceaf225e179651397431
- License
- Not declared
- Collected
- 2026-07-28
- Default branch
- main
View the original SKILL.md
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.