gh-address-comments
by openaigh-address-comments helps address review and issue comments on the open GitHub PR for your current branch using gh CLI. It verifies GitHub auth first, fetches comments and review threads, numbers them, and helps you choose which items to fix. Useful for gh-address-comments guide and gh-address-comments for PR Review workflows.
This skill scores 78/100, which means it is a solid directory candidate: users get a clearly triggerable workflow for addressing comments on the open GitHub PR for the current branch, with enough operational detail to know when to install it and what it will do. It is useful for agent-driven PR cleanup, though not fully polished for broader adoption.
- Clear triggerability: it targets the open PR for the current branch and explicitly tells the agent to verify `gh` authentication first.
- Concrete workflow: includes a step-by-step process and a helper script (`scripts/fetch_comments.py`) to fetch PR comments, reviews, and inline threads.
- Good install decision value: the description and default prompt make the intended use case obvious—address actionable GitHub PR review comments and summarize updates.
- Depends on `gh` auth and elevated network access, so it may fail in constrained environments unless permissions are handled correctly.
- Operational guidance is fairly narrow: it covers inspection and selection of comments, but leaves the actual fix-application workflow mostly implicit.
Overview of gh-address-comments skill
What gh-address-comments does
gh-address-comments helps you find and work through actionable comments on the open GitHub PR for your current branch, using gh and the repository’s review threads as the source of truth. It is built for the moment when a PR has feedback scattered across review threads, and you want a structured way to identify what to fix before editing code.
Who this skill is for
Use the gh-address-comments skill if you already have a branch with an open PR and need to respond to review or issue comments without manually hunting through GitHub. It is most useful for maintainers, contributors, and agents doing PR cleanup when the main problem is comment triage, not broad refactoring.
Why it’s different
The skill is not just “read the PR and edit files.” It first checks GitHub auth, then fetches the comments and review threads, numbers them, summarizes the work required, and asks which items to address. That makes gh-address-comments better for selective PR review work than a generic prompt that assumes every comment should be fixed.
How to Use gh-address-comments skill
Install gh-address-comments
Install the gh-address-comments skill in your skills environment, then make sure the repo you want to work on is checked out locally and linked to the GitHub PR you want to inspect. The gh-address-comments install step is only useful if your environment supports skills from openai/skills; the skill itself depends on gh being available and authenticated.
Prepare the right input
For best gh-address-comments usage, start with a branch that already has an open PR on GitHub. The skill needs the current branch context, and it works best when your request names the PR goal clearly, such as “address the review comments on this branch” or “triage actionable comments on the open PR.”
Suggested workflow
- Confirm
gh auth statusworks with the scopes needed for repo and workflow access. - Run the skill to fetch comments and review threads.
- Review the numbered list and the fix summary.
- Choose which items to address first.
- Apply changes, then re-check the PR discussion for anything remaining.
Files to read first
Start with SKILL.md for the intended flow, then inspect scripts/fetch_comments.py to understand how comments are collected. Also review agents/openai.yaml for the default prompt and tool framing. In this repository, those three files give the most useful gh-address-comments guide context without forcing you to read the entire tree.
gh-address-comments skill FAQ
Does gh-address-comments work without gh auth?
No. gh-address-comments expects gh auth login to be set up first, and the workflow explicitly verifies auth before querying the PR. If auth fails or the token lacks required scopes, the skill should prompt for re-authentication rather than guessing.
Is this better than a normal prompt?
Yes, when the task is PR-specific and comment-driven. A normal prompt can describe how to fix a review, but gh-address-comments for PR Review adds a repeatable intake step: fetch threads, number them, summarize impact, and let the user choose what to tackle.
When should I not use it?
Do not use gh-address-comments if there is no open PR for the current branch, if you need to redesign the feature from scratch, or if the comments are purely conversational and not actionable. It is also a poor fit when you want an automatic bulk-edit of every comment without review.
Is it beginner-friendly?
Yes, if the user can work with GitHub PRs and basic CLI auth. The skill lowers the cognitive load by turning review noise into a numbered decision list, but it still assumes you can inspect code and decide which comments are worth addressing.
How to Improve gh-address-comments skill
Give the skill narrower targets
The strongest gh-address-comments results come from specifying what counts as actionable. If you know you only want style fixes, API corrections, or logic changes, say that up front. That helps the skill prioritize comments that matter and avoid spending time on optional suggestions.
Include context that changes the fix
When a review comment depends on product behavior, compatibility, or test constraints, include that context in your request before the skill starts editing. For example: “Preserve backward compatibility,” “do not change public interfaces,” or “keep the fix limited to this branch.” This improves the first pass more than generic “be careful” guidance.
Watch for common failure modes
The main risks in gh-address-comments are stale threads, auth issues, and over-fixing comments that should be discussed instead of implemented. If the fetched list looks incomplete or the branch PR changed recently, rerun the fetch step before editing. If a comment is ambiguous, ask for clarification before patching.
Iterate after the first pass
After applying the selected fixes, re-open the PR thread list and compare the remaining comments against the changes you made. For gh-address-comments skill workflows, the fastest improvement loop is: fetch, choose, fix, re-check, then refine only the comments that still block approval.