gh-pr-review-comments
Address PR Review Comments
Use this skill to run a full GitHub PR review follow-up pass from live comment data instead of screenshots or pasted summaries. Fetch the comments, decide what to accept, update only the current PR branch, resolve threads deliberately, and finish with the exact status line the user expects.
Boundary Rules
- This skill addresses existing review comments on the current PR branch. It does not run a fresh end-to-end critique of the implementation plan.
- If the user wants a broader challenge of the plan, branch approach, or test strategy beyond the current review comments, use
gh-plan-review.
Core Workflow
- Confirm you are already on the PR feature branch you intend to update, not
main,master, or another default branch. - Fetch the authoritative review comments with
gh api --paginate repos/{owner}/{repo}/pulls/{pr}/comments. - Exclude reply comments such as items with
in_reply_to_idbefore triaging, so you classify top-level review requests rather than thread replies. - Classify every remaining review comment before touching code.
- Inspect the relevant files, diff, and surrounding context for accepted comments.
- Apply only the accepted fixes on the same PR branch.
- Run the smallest relevant verification for the touched code.
- Determine whether the PR branch has exactly one branch commit or multiple branch commits relative to the PR base. A multi-commit PR branch must not default to amend or force-push.
More from beeman/skills
feature-structure
Use when reorganizing code around feature boundaries, splitting monolithic screen components or state hooks, deciding whether logic belongs in data-access, feature, ui, or child features, or moving orchestration out of prop-heavy UI files.
8gh-pr-create
Create a GitHub pull request from local repo changes. Use when Codex must get feature-branch setup and local commit packaging from `gh-commit`, get approval before pushing, show the exact PR title and body that will be sent, handle single-commit and multi-commit branch flows explicitly, and open or update the PR with gh.
7gh-issue-kickoff
Kick off work on a GitHub issue with gh. Use when Codex needs to start from the authoritative issue state and local codebase, fix only material issue gaps, and produce the first execution-ready implementation plan. For a deeper critique or tradeoff review of an existing plan, use `gh-plan-review`.
5gh-plan-review
Review, challenge, pressure-test, or refine an implementation plan tied to a GitHub issue, GitHub PR, or active branch. Use when Codex needs to inspect the authoritative GitHub state and local repo context, run a scope challenge, identify material plan risks, surface real tradeoffs, and finish with a fixed review summary without mutating code or git state.
5gh-pr-rebase
Rebase an existing GitHub PR branch onto the repository default branch. Use when Codex needs to fetch the latest default-branch history, keep the local default branch current when that is safe, rebase the current feature branch, resolve straightforward conflicts carefully, ask the user to decide ambiguous conflicts, and update the remote PR branch with `git push --force-with-lease` after any required approval.
5gh-commit
Prepare a local Git commit from repo changes. Use when Codex needs to get onto the correct feature branch if needed, inspect `git status --short`, the current diff, and branch history, run the smallest relevant verification, add any required changeset, and package the tracked work into either a new commit or an explicitly approved amend flow before any push or PR step.
4