home / skills / openai / skills / gh-address-comments
This skill helps you identify, review, and address open PR comments on the current branch using gh, with authentication checks.
npx playbooks add skill openai/skills --skill gh-address-commentsReview the files below or copy the command above to add this skill to your agents.
---
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.
This skill helps you find the open GitHub pull request for the current branch and address its review and issue comments using the gh CLI. It verifies that gh is authenticated and prompts you to authenticate if needed. The skill guides you through inspecting comment threads, selecting which comments to address, and applying fixes automatically where possible.
It first checks gh authentication and asks you to run gh auth login if not authenticated or if scopes are insufficient. It runs a script to fetch and summarize all review threads and comments on the PR, numbers them, and asks which items you want to address. For chosen comments it attempts to apply fixes, and if gh reports auth or rate limits mid-run it prompts for re-authentication and retries.
What if gh auth status is blocked by sandboxing?
Rerun the check with elevated permissions (sandbox_permissions=require_escalated) or run gh auth login outside the sandbox to grant required scopes.
What happens if a fix causes a merge conflict?
The skill will surface the conflict so you can resolve it manually; automatic fixes stop before making conflicting changes.