skills/answer-reviewer-questions/SKILL.md
For each reviewer question on a PR, recall implementation reasoning and compose a raw answer. Use when the user asks to "answer reviewer questions", "draft answers to PR questions", or "explain reviewer questions".
npx skillsauth add tobihagemann/turbo answer-reviewer-questionsInstall this skill globally with one command. Works with Claude Code, Cursor, and Windsurf.
3 of 9 scanners reported clean
Some scanners were skipped, did not run, or reported a non-clean status. Review each row below.
For each reviewer question thread, recall the implementer's reasoning and compose a raw answer. The answers are plain text and feed into a downstream reply-drafting skill that applies voice rules and reply formatting.
Use the question threads from conversation context. Each thread has: thread id, file path, line (use originalLine when line is null), the reviewer's original comment, and the reconciled intent from /interpret-feedback.
If no question threads were provided, report that there are no questions to answer and stop.
For each thread:
/recall-reasoning skill with <path>:<line>. It returns either recalled reasoning from a past transcript, or a fallback derived from reading the commit diff and surrounding code.Output one block per thread:
**Thread <id>** (<path>:<line>)
<answer text>
_Grounding: derived from current code_
Include the _Grounding:_ line only when /recall-reasoning returned no transcript. Omit it when the answer is grounded in recalled reasoning.
Then use the TaskList tool and proceed to any remaining task.
/github-voice or apply reply formatting. Downstream drafting applies voice rules when composing the actual reply./recall-reasoning returned no transcript, still compose an answer from the current code and include the _Grounding:_ line so the downstream drafter knows the answer has weaker grounding.tools
Teach the user to deeply understand a change through interactive tutoring: restating understanding, drilling into why/what/how, and quizzing until mastery. The active counterpart to a one-shot explanation. Use when the user asks to "understand this change", "teach me this change", "help me understand what changed", "walk me through this change", "make sure I understand this", "quiz me on this", or "teach me what we did".
tools
Teach the user to deeply understand a change through interactive tutoring: restating understanding, drilling into why/what/how, and quizzing until mastery. The active counterpart to a one-shot explanation. Use when the user asks to "understand this change", "teach me this change", "help me understand what changed", "walk me through this change", "make sure I understand this", "quiz me on this", or "teach me what we did".
tools
Update an existing GitHub pull request's title and description to reflect the current state of the branch. Use when the user asks to "update the PR", "update PR description", "update PR title", "refresh PR description", or "sync PR with changes".
tools
Execute an approved split plan by creating separate branches, commits, and PRs for each change group. Use when the user asks to "split and ship", "ship the split plan", "create separate PRs", or "split changes into branches".