reply-to-pr-threads

# Reply to PR Threads Draft replies for a processed review-thread list, confirm with the user, and post the surviving drafts. ## Step 1: Re-fetch Thread State Auto-detect owner, repo, and PR number from the current branch if not provided, then query the current resolution state: ```bash gh api graphql -f query=' query($owner: String!, $repo: String!, $pr: Int!) { repository(owner: $owner, name: $repo) { pullRequest(number: $pr) { reviewThreads(first: 100) { nodes { id isResolved } } } } }' -f owner='{owner}' -f repo='{repo}' -F pr={pr_number} ``` Drop threads whose `isResolved` is now true. Reviewers or bots such as CodeRabbit may resolve threads after the original fetch, and drafting replies for them is wasted work. ## Step 2: Run `/github-voice` Skill Run the `/github-voice` skill to load voice rules and the insider-vs-outsider detection. ## Step 3: Draft Replies Use the processed-thread list from conversation context. Each entry has: thread id, file path, line, category (`fix`, `skip`, `answer`, or `clarify`), and per-category payload. Keep every reply to one or two sentences. No bullet-point reasoning. No bolded labels. **fix**: payload is a commit SHA, optionally with a divergence note. ``` Fixed in <commit-sha>. ``` Only add a brief sentence after the SHA when the fix meaningfully diverges from what the reviewer suggested. Otherwise the SHA alone is enough. **skip**: payload is the skip reasoning. State the reasoning directl...