{"id":"pr-threads-address","name":"pr-threads-address","summary":"現在の支部のPRで未解決のPRレビュースレッドをすべて体系的に処理し、各コメントを分析し、要求されたコード変更(必要ならテスト付き)を行い、コミットし、必要に応じて返信と解決を行います。","body":"## Prerequisites\n\n### gh pr-review extension\n\nBefore using this command, check if the gh pr-review extension is installed:\n\n```bash\ngh extension list | grep -q pr-review || gh extension install agynio/gh-pr-review\n```\n\n### Resolve PR context\n\nEvery `gh pr-review` subcommand requires both `--pr <number>` and `--repo <owner/repo>` — do not omit either. Look the values up once at the start of the workflow and substitute the literal numbers and slugs into every later command.\n\nGet the PR number for the current branch:\n\n```bash\ngh pr view --json number -q .number\n```\n\nGet the repository slug:\n\n```bash\ngh repo view --json nameWithOwner -q .nameWithOwner\n```\n\nThen pass the resulting values directly — e.g. `--pr 42 --repo posit-dev/skills` — on every subsequent `gh pr-review` call in this workflow (review view, comments reply, threads resolve, etc.).\n\n## Workflow\n\n1. Fetch and display all unresolved PR review threads\n2. Analyze each thread to understand the requested changes\n3. For each thread:\n   1. Make the necessary code modifications\n   2. (When possible) Add unit tests to verify the change\n   3. Commit the changes with descriptive commit messages using conventional commit specification\n4. Report back with a summary of addressed threads\n5. Ask if the user wants to resolve the threads. If so, reply to each thread indicating what was done and then resolve the thread.\n\n## CLI Reference\n\n### View PR Reviews and Comments\n\nDisplay all reviews, inline comments, and replies for a pull request:\n\n```bash\ngh pr-review review view --pr <number> --repo <owner/repo>\n```\n\n**Common filters:**\n\n- `--reviewer <login>` — Filter by specific reviewer\n- `--states <list>` — Comma-separated review states (APPROVED, CHANGES_REQUESTED, COMMENTED, DISMISSED)\n- `--unresolved` — Show only unresolved threads\n- `--tail <n>` — Show only the last n replies per thread\n- `--include-comment-node-id` — Include GraphQL node IDs for replies\n\n### Reply to Review Threads\n\n```bash\ngh pr-review comments reply --thread-id <PRRT_...> --body \"<reply-text>\" --repo <owner/repo> --pr <number>\n```\n\nFor multi-line replies, pass `--body \"$(cat <<'EOF' ... EOF\\n)\"` heredoc syntax.\n\n### Resolve a Thread\n\n```bash\ngh pr-review threads resolve --thread-id <PRRT_...> --pr <number> --repo <owner/repo>\n```\n\nThread IDs (format `PRRT_...`) come from `review view --include-comment-node-id`.","author":"@posit-dev","ownerProfile":null,"authorContacts":null,"sourceUrl":"https://github.com/posit-dev/skills/tree/main/github/pr-threads-address","license":"MIT","category":"document","lang":"en","tokens":588,"stars":0,"calls30d":3,"claimed":false,"visibility":"public","origin":"crawler","version":"0.1.0","createdAt":"2026-08-22","updatedAt":"2026-08-22","files":[],"requires":{"mcp":[],"tools":[]},"safety":{"flags":[],"scannedAt":"2026-08-22","hasScripts":false,"networkEndpoints":[]}}