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.development
Apply a UX lens to a user-facing change: whether it serves the user's real goal and whether the path through it holds together, using the Understanding, Bridging, and Flowing contexts. Use when scoping, planning, or assessing any change that affects what a user sees or does. Loaded as a lens during planning and assessment.
development
Apply a UX lens to a user-facing change: whether it serves the user's real goal and whether the path through it holds together, using the Understanding, Bridging, and Flowing contexts. Use when scoping, planning, or assessing any change that affects what a user sees or does. Loaded as a lens during planning and assessment.
development
Assess project-wide structural technical debt: complexity hotspots, deprecated API usage, duplication clusters, and architecture rot. Ranks findings by impact and refactor effort into a report at .turbo/technical-debt.md. Use when the user asks to "assess technical debt", "find technical debt", "review technical debt", "what should we refactor", "find refactoring candidates", "where is the code rot", or "what's our worst code". Analysis-only — does not modify code.
development
Run a multi-agent review of code comments and markdown documentation for unnecessary content, then fix the issues. Covers what-restating comments, name-mirroring doc comments, status-update prose, and other documentation noise. Use when the user asks to "simplify docs", "simplify documentation", "clean up comments", "clean up docs", "review documentation", "strip unnecessary comments", "reduce doc noise", or "run simplify-docs".