gh-address-comments — Claude Code skill: what it does, how to install
gh-address-comments finds the open pull request on your current branch, lists its review comments, and fixes the ones you pick.
Apache-2.0 ★ 7,191 updated 2026-10-24
npx skills add tech-leads-club/agent-skills --skill gh-address-comments -a claude-codeWhat gh-address-comments does
The skill takes the pull request that is already open for the branch you are on. It runs scripts/fetch_comments.py, and that script prints every comment and review thread attached to the PR.
Threads come back numbered, each with a short note on what a fix would involve. You choose the numbers. Only those get edited, so a single remark about indentation does not turn into a rewrite of the whole branch.
Auth is checked first with gh auth status; when that fails, the skill tells you to run gh auth login. Without a logged-in gh the first command errors out. If login or GitHub rate limits break mid-run, it asks you to sign in again and retries. Opening pull requests, chasing a red CI build (that job belongs to gh-fix-ci), and routine Git work are outside its scope.
What it helps with
- clear a pile of review comments on an open pull request
- get each thread numbered with a note on the fix it needs
- work through reviewer feedback without switching to the browser
- finish the last round of fixes before merging
Example prompts for the agent
- Address the review comments on this PR and show me the threads first.
- Fix the review feedback on the current branch.
- Handle the PR comments, but only items 2 and 4.
How to install gh-address-comments
1Skills CLI (Vercel)
npx skills add tech-leads-club/agent-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 tech-leads-club/agent-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 tech-leads-club/agent-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 tech-leads-club/agent-skills 'packages/skills-catalog/skills/(development)/gh-address-comments'2Manually: put the files in place
.github/skills/gh-address-comments/SKILL.md1Skills CLI (Vercel)
npx skills add tech-leads-club/agent-skills --skill gh-address-comments -a gemini-cli2Platform CLI
gemini skills install https://github.com/tech-leads-club/agent-skills --path 'packages/skills-catalog/skills/(development)/gh-address-comments'Manually: put the files in place
.devin/skills/gh-address-comments/SKILL.mdThe legacy .windsurf/skills/ path still works
Claude.ai
Zip the folder and upload it in Settings → Capabilities → Skills
Step by step, with commands for each platform: How to install skills in Claude Code: five ways
Questions about gh-address-comments
How do I install gh-address-comments in Claude Code?
Run npx skills add tech-leads-club/agent-skills --skill gh-address-comments -a claude-code. The skill file then sits at ~/.claude/skills/gh-address-comments/SKILL.md.
What does gh-address-comments do?
It locates the open PR for your branch, prints its comments and review threads with numbers, and applies code fixes to the ones you select.
Does it need the gh CLI signed in?
Yes. Check with gh auth status and run gh auth login if the check fails, otherwise the skill stops at the first step.
Source text
SKILL.md · Apache-2.0
--- name: gh-address-comments description: Address review and issue comments on the open GitHub PR for the current branch using gh CLI. Use when user says "address PR comments", "fix review feedback", "respond to PR review", or "handle PR comments". Verifies gh auth first and prompts to authenticate if not logged in. Do NOT use for creating PRs, CI debugging (use gh-fix-ci), or general Git operations. metadata: author: github.com/openai/skills version: '1.0.0' 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. **Prerequisites:** Ensure `gh` is authenticated before running commands. Check authentication status with `gh auth status`. If not authenticated, instruct the user to run `gh auth login` to authenticate with GitHub. ## 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.
© github.com/openai/skills · Apache-2.0 · tech-leads-club/agent-skills