github-pr-resolvelisted

# PR Review Resolver Evaluate PR review comments, triage with the user, implement agreed fixes. ## Phase 1 — Validate & gather If `$ARGUMENTS` is empty or not a number, ask via `AskUserQuestion`: *"Which PR number would you like me to resolve review comments for?"* ```bash bash "${CLAUDE_SKILL_DIR}/scripts/gather-pr-comments.sh" $ARGUMENTS ``` Returns `{pr, inline_threads, review_summaries, stats}` where: - `pr` — title, branches, state, url - `inline_threads` — code-level comments grouped by thread (root + replies) - `review_summaries` — top-level review bodies (approve/request changes/comment) - `stats` — counts On `error`, stop. If `stats.total_threads == 0 && stats.total_review_summaries == 0`, say "No review comments found on PR #N" and stop. If `stats.total_threads > 30`, show a per-file summary table first and proceed file-by-file. ## Phase 2 — Display comments **Review summaries** (if any), first: ``` ### Review by @{author} — {state} > {body} ``` `state` ∈ {APPROVED, CHANGES_REQUESTED, COMMENTED}. **Inline threads**, grouped by file: ``` ### Thread {n} — {path}:{line} (by @{author}) > {root body} Code context: {diff_hunk — last 5 lines only} ``` Show replies indented: ` ↳ @{reply_author}: {reply body}`. Replies often contain resolution or agreement — important for triage. ## Phase 3 — Triage For each thread, ask via `AskUserQuestion`: - Brief analysis of what the reviewer is suggesting (interpret if technical or unclear). - Include reply context if i