Inline comments, general discussion and follow-up replies can make a review hard to track. gh-address-comments collects feedback from the PR associated with the current branch, numbers the items and explains the likely changes. You select the scope before implementation, which makes it useful for a review round without treating every suggestion as an automatic requirement.
Install and prepare
This guide covers the standalone Skill retained in openai/skills. That repository is deprecated and current examples have moved to openai/plugins; the instructions here describe the linked standalone version, not the latest plugin.
Enter this line in the Codex conversation, not a terminal. If the installed Skill does not appear, restart Codex.
$skill-installer gh-address-comments
- A local Git checkout on the target PR branch
- GitHub CLI gh installed with repository access
- Permission to read the PR and edit your working copy
Run gh auth status in the terminal. If needed, use gh auth login and complete browser authorization. The account and its permissions determine which private PRs are accessible. [4]
Try a first task
In the target PR branch, start by requesting a review checklist:
$gh-address-comments
Read the review feedback on the current branch’s PR. First number the items and show the file, discussion conclusion and proposed change for each. Flag stale or duplicate feedback. Wait for my selected numbers before editing. Preserve existing uncommitted work; do not post replies or merge the PR automatically.
Work through the task
-
Confirm the PR. Check the repository and branch, then verify the PR URL so feedback from another worktree is not mixed in.
-
Select the actionable feedback. Choose items from the numbered list. Resolve conflicting suggestions before asking for implementation.
-
Review each change. Ask for a mapping from selected comments to diffs and relevant checks, with unhandled items listed separately. Arrange posting and review replies as a separate step.
Process a review without losing track of threads
Start from the target PR branch and confirm the account with gh auth status. Give Codex the PR URL and ask for a numbered list of threads, reviewer, affected file, requested change and current status. Reviews can include stale suggestions, questions rather than requests, and conflicting advice. Select the numbers to act on before editing. For example: “Address threads 2 and 4 only; explain why thread 3 conflicts with the current API contract before changing it.”
For each selected thread, inspect both the original diff and the current code. A line number from an older revision may no longer represent the implementation. Then run the test or manual reproduction most relevant to that comment. Ask for a compact “thread → changed location → validation” mapping so the next reviewer can tell what was addressed and what still needs discussion.
Know what completion means
A local patch is not a GitHub reply, branch push or resolved review thread. Before calling the task done, inspect the working diff, failed checks and remaining thread numbers. Posting a reply or pushing is a separate action to request explicitly. If the comment-fetching script cannot read the discussion, verify that the branch has an open PR and the authenticated account can access it; a notification excerpt is not enough to reconstruct a review thread.
Another case: two review requests interact
Imagine one reviewer asks to “remove duplicate data fetching” while another wants the list refreshed after every save. Ask: “List the code and expected behavior behind both threads before editing. Explain whether they really conflict and propose the smallest way to satisfy both.” Read the full threads and current diff before choosing a code change, test or clarification reply. Afterward, check refresh timing, request count and failure states; removing a request should not leave the saved list stale. If a later commit already resolved a thread, mark it addressed in the numbered summary instead of changing code again.
Check the result
The useful handoff maps each feedback number to changed files and validation results. Compare the diff with the original comment, and look for unrelated refactoring. Summarizing feedback or changing code does not by itself mean the review thread has been resolved on GitHub.
Common blockers
No current PR is found. Check that the branch has an open PR. Supply the exact link and check out the matching branch when necessary.
Authentication fails or comments are missing. Check the gh account, repository permissions and rate limit before drawing conclusions from incomplete threads.
A comment is stale. Compare it with current code before deciding whether to implement it or explain why it no longer applies.
If the helper appears missing, check the skill directory
If fetch_comments.py appears missing, check whether the agent searched the project repository instead of the installed skill directory. A Codex App user reported repeated GraphQL fallbacks even though the helper existed under the skill’s scripts/ folder. After fetching comments, revisit the original PR to confirm each thread’s location and unresolved status before editing.