Draft replies for a processed review-thread list, confirm with the user, and post the surviving drafts.
\nAuto-detect owner, repo, and PR number from the current branch if not provided, then query the current resolution state:
\ngh api graphql -f query='\nquery($owner: String!, $repo: String!, $pr: Int!) {\n repository(owner: $owner, name: $repo) {\n pullRequest(number: $pr) {\n reviewThreads(first: 100) {\n nodes { id isResolved }\n }\n }\n }\n}' -f owner='{owner}' -f repo='{repo}' -F pr={pr_number}\nDrop 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.
$github-voice SkillRun the $github-voice skill to load voice rules and the insider-vs-outsider detection.
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.
\nfix: payload is a commit SHA, optionally with a divergence note.
\nFixed in <commit-sha>.\nOnly add a brief sentence after the SHA when the fix meaningfully diverges from what the reviewer suggested. Otherwise the SHA alone is enough.
\nskip: payload is the skip reasoning. State the reasoning directly. Do not apologize.
\nanswer: payload is raw answer text from $answer-reviewer-questions. Tighten to one or two sentences and apply $github-voice rules. Do not cite transcripts or mention Claude. The reply reads as the implementer's own explanation.
clarify: payload is a user-directed question. Draft it as directed.
\nOutput all drafts as text, grouped by file:
\n### <file-path>\n\n**Thread <id>** (<category>, line <line>)\nReviewer: <original comment, truncated if long>\nReply: <drafted reply>\nThen use request_user_input to ask whether to post. Offer:
For each approved draft, write the drafted reply to .turbo/pr/thread-<thread-id>.md with apply_patch, then post via the reply mutation:
gh api graphql -f query='\nmutation($threadId: ID!, $body: String!) {\n addPullRequestReviewThreadReply(input: {pullRequestReviewThreadId: $threadId, body: $body}) {\n comment { id }\n }\n}' -f threadId='<thread-id>' -F body=@.turbo/pr/thread-<thread-id>.md\nSubstitute <thread-id> with the thread's id for each post.
Report the outcome as a table, one row per thread, keeping every cell to a single line:
\n| Thread | \nCategory | \nOutcome | \n
|---|
Where Outcome is one of:
\nKeep the report to the table. When the table would be empty, report one line stating that no replies were posted and why instead.
\nThen call update_plan to mark this step completed and continue with the next step of the active workflow.