github-pr-resolvelisted

# PR Review Resolver Evaluate PR review comments, triage with the user, implement agreed fixes, and reply on every handled thread. **Arguments:** `$ARGUMENTS` — PR number, optionally followed by `-all` to include resolved threads and threads you already answered (default: only threads awaiting your reply). ## Phase 1 — Validate & gather If `$ARGUMENTS` has no PR 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, current_user, inline_threads, review_summaries, project_rules, stats}` where: - `pr` — title, branches, state, url - `inline_threads` — code-level threads (root + replies), each with `thread_node_id`, `is_resolved`, `is_outdated`, `awaiting_reply`. Without `-all`, only unresolved threads whose last comment is not yours. - `review_summaries` — top-level review bodies (approve/request changes/comment) - `project_rules` — `CLAUDE.md`, `REVIEW.md` and `.claude/rules/*.md` from the repo root and every folder above a commented file, keyed by repo-relative path - `stats` — counts, including `total_threads_on_pr`, `resolved_threads`, `answered_threads`, `outdated_threads` On `error`, stop. If `stats.total_threads == 0 && stats.total_review_summaries == 0`, say "No review comments awaiting a reply on PR #N" — mention `resolved_threads` / `answered_threads` and that `-all` includes them — and stop. If `stats.total_threads > 3