gh-pr-consider-commentslisted

Pull unresolved review comments on a pull request, read them alongside the diff and any suggested changes, and discuss the response with the user before touching any code — then, once agreed, implement, commit, push, and reply to/resolve the threads. Use whenever the user wants to work through PR feedback — phrases like "look at the PR comments", "what's outstanding on my PR", "go through the review feedback", "address the comments on #123", or right after a reviewer leaves comments. Optional argument is a PR number or URL; otherwise auto-detects from session context or the current branch. This skill is discussion-first — it never implements or acts on threads without agreeing an approach first.
jdrydn/dotclaude · ★ 0 · Code & Development · score 73

Install: claude install-skill jdrydn/dotclaude

# Consider GitHub PR Comments Pull the **unresolved** review threads on a pull request, read each one against the diff and any suggested change, then **discuss the plan with the user before writing any code**. Once an approach is agreed, carry it through: implement the agreed changes, offer to commit & push, then offer to reply to and resolve the threads. The discussion gate always comes first — nothing is written or posted until the user agrees. ## Arguments 1. **PR** _(optional)_ — a PR number (`123`), a full URL (`https://github.com/OWNER/REPO/pull/123`), or nothing (auto- detect from session context or the current branch). ## Tools required - `gh` CLI (authenticated) — for the PR, its diff, the review threads (GraphQL), and posting replies/resolving threads. - `git` — for pushing after committing. - `AskUserQuestion` — to confirm before the outward-facing actions (push, reply, resolve). ## Steps ### 1. Resolve the PR Try in order, stop at the first hit: **a) Explicit argument** — if the user gave a number or URL, use it. Extract `OWNER`, `REPO`, and the number. **b) Current session context** — if a PR was raised, pushed, or discussed earlier in this same conversation (e.g. the user opened/reviewed a PR a few turns ago), use that PR. You already have its number and URL in context — don't re-derive it. When the user says "the PR" right after this kind of activity, they mean that one. **c) Current branch** — ```bash gh pr view --json number,title,url,headRefNa