gh-address-comments — Claude Code skill: install and use
This skill finds the open pull request for the current branch, lists review comments, and applies the fixes you select through gh.
npx skills add openai/skills --skill gh-address-comments -a claude-codeWhat gh-address-comments does
The skill locates the open pull request for the current branch and runs scripts/fetch_comments.py to print its comments and review threads. The agent numbers each item, gives a short description of the required fix, and asks which comments to address.
After you choose the comments, the agent applies the related changes. It checks gh auth status first and asks you to run gh auth login when authentication fails. gh commands need elevated network access, with workflow and repo scopes available. Without an authenticated gh session, this workflow stops.
What it helps with
- find the open pull request for the current branch
- list review comments and discussion threads
- number comments that need attention
- choose specific review comments to address
- apply fixes for selected comments
Example prompts for the agent
- Check `gh` authentication, find the open pull request for the current branch, and list its comments with `scripts/fetch_comments.py`.
- Number the review threads, summarize the fix needed for each one, and ask me which comments to address.
- Apply the fixes for comments 1 and 3, then check the result.
How to install gh-address-comments
1Skills CLI (Vercel)
npx skills add openai/skills --skill gh-address-comments -a claude-code2Manually: put the files in place
~/.claude/skills/gh-address-comments/SKILL.mdCopy the whole skill folder; for one project use .claude/skills/gh-address-comments/
1Skills CLI (Vercel)
npx skills add openai/skills --skill gh-address-comments -a codex2Manually: put the files in place
.agents/skills/gh-address-comments/SKILL.mdFor all projects use ~/.agents/skills/
1Skills CLI (Vercel)
npx skills add openai/skills --skill gh-address-comments -a cursor2Manually: put the files in place
.cursor/skills/gh-address-comments/SKILL.mdCursor also reads .agents/skills/ and .claude/skills/
1GitHub CLI
gh skill install openai/skills gh-address-comments2Manually: put the files in place
.github/skills/gh-address-comments/SKILL.md1Skills CLI (Vercel)
npx skills add openai/skills --skill gh-address-comments -a gemini-cli2Platform CLI
gemini skills install https://github.com/openai/skills --path skills/.curated/gh-address-commentsManually: put the files in place
.devin/skills/gh-address-comments/SKILL.mdThe legacy .windsurf/skills/ path still works
Skills CLI (Vercel)
npx skills add openai/skills --skill gh-address-comments -a opencodeClaude.ai
Zip the folder and upload it in Settings → Capabilities → Skills
From the same set20
The whole set →Similar
Questions about gh-address-comments
How do I install gh-address-comments in Claude Code?
Run npx skills add openai/skills --skill gh-address-comments -a claude-code, run npx skills add openai/skills --skill gh-address-comments -a claude-code again, then check ~/.claude/skills/gh-address-comments/SKILL.md.
What does gh-address-comments do?
It finds the open pull request for the current branch, prints comments and review threads with scripts/fetch_comments.py, numbers them, and applies fixes for the comments you select.
What does gh-address-comments require?
gh must be authenticated with the workflow and repo scopes. If gh auth status or another gh command is blocked by network restrictions, elevated network access is required.
Source text
SKILL.md · Apache-2.0
--- name: gh-address-comments description: 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. metadata: short-description: Address comments in a GitHub PR review --- # 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.
© openai · Apache-2.0 · openai/skills