gh-address-comments
💡 Summary
An AI agent skill that uses the GitHub CLI to fetch, summarize, and help address comments on an open pull request for the current branch.
🎯 Target Audience
🤖 AI Roast: “This skill is like a concierge that can only point you to the hotel door, but you still need to find the key, open it, and carry all your own luggage.”
The skill requires escalated network permissions to run `gh` commands, posing a risk of unauthorized repository access or data exfiltration if the agent's environment is compromised. Mitigation: Implement strict, scope-limited OAuth tokens for the `gh` CLI and run the agent in a network-restricted sandbox.
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.
Pros
- Automates the tedious process of collating PR feedback.
- Leverages the widely-used and official GitHub CLI tool.
- Provides a structured workflow for addressing comments.
Cons
- Heavily dependent on the user's local `gh` CLI setup and authentication.
- Lacks detail on how fixes are actually applied.
- Assumes a specific repository structure with a `scripts/` directory.
Disclaimer: This content is sourced from GitHub open source projects for display and rating purposes only.
Copyright belongs to the original author openai.