Dictating code review comments on GitHub
A good review comment explains what you noticed, why it matters and what you'd do instead. Typed, that often shrinks to "nit: rename". Spoken, it comes out whole, sometimes too whole. Here's how to use voice for GitHub pull request reviews without sending a wall of text, and which parts still belong on the keyboard.
Why reviews are a good fit for voice
Reviewing is mostly reading. You scroll a diff, notice something, and then have to switch into writing mode to explain it. That switch is where comments get short and cryptic. Saying the thought while it's fresh is quicker, and it usually carries the reasoning that makes a comment useful to the author.
The risk runs the other way. Spoken comments come out longer and more conversational than written ones, and tone is easier to misjudge when you didn't pick each word. A review needs a pass of editing before anyone sees it.
Use a pending review as your buffer
GitHub gives you that pass for free. Hover over a line in Files changed and click the blue comment icon, or drag across line numbers (or Shift-click the last one) to comment on a range. Write your first comment and click Start a review. After that, each comment is added with Add review comment.
GitHub's docs say these comments stay pending and only visible to you until you submit. So you can dictate freely as you go through the files, then read the whole set before anything is published. When you're done, choose Comment, Approve or Request changes and click Submit review.
A spoken shape for a comment
Four beats cover most comments, and they're easy to say in order:
- What you see: "This retries forever if the token endpoint is down."
- Why it matters: "On a bad day that keeps every worker busy."
- What you'd do: "I'd cap it at three attempts with a backoff."
- How strongly you mean it: "Not blocking, happy to do it in a follow-up."
The last beat is the one people forget when typing, and it saves a round of "is this required?" replies.
Keep the keyboard for these
- Suggested changes. Press Command+G to insert a suggestion block and type or paste the code. Don't dictate code.
- Quoting. Select text in the thread and press R to quote it in your reply, then dictate the answer.
- Preview. Command+Shift+P toggles Write and Preview, which shows you how backticks and lists will render.
- Posting. Command+Enter submits a comment. Read first.
- Stock phrases. Saved replies (Ctrl+., then Ctrl and the reply's number) are faster than dictating the same sentence for the tenth time.
Identifiers inside a sentence are the other weak spot. Type them in backticks, or add your project's names to your dictation tool's vocabulary so they come out spelled right.
Reviews from the terminal
The GitHub CLI can leave a review without opening the browser. From the docs:
gh pr review 123 --comment -b "Looks good, one question about the retry cap."
gh pr review 123 -r -b "Retries need a cap before this ships."
gh pr review --approve
Dictating into the quotes works for one sentence. For a longer review, dictate it into a note first, copy it and pipe it in, since -F - reads the body from standard input:
pbpaste | gh pr review 123 --comment -F -
That also keeps the text away from shell quoting, which matters as soon as a sentence contains an apostrophe or a dollar sign.
With FnFlow
FnFlow works in the GitHub comment box like in any other text field. Hold fn (or right ⌘), talk, let go, and the comment is pasted at the cursor. It reads the field back and tells you whether the text landed, and if you switched tabs mid-dictation, the text waits in history with its audio. Recognition runs on your Mac, which matters if the code under review is private. More on that in private dictation for work.
It doesn't format anything. FnFlow types your words with punctuation and capitals, without Markdown, suggestion blocks or a tone pass. That's deliberate, since you're the one who knows how blunt a comment should be. The editing is still yours. For the same approach applied to prompts, see how to dictate a good prompt.
Questions
Can people see my review comments while I'm still dictating?
Not if you use a review. GitHub's docs say line comments are pending and only visible to you until you submit the review. A single comment posted outside a review is visible right away.
How do I dictate a suggested change?
Dictate the explanation, then press Command+G (GitHub's shortcut for inserting a suggestion) and type or paste the code inside the suggestion block. Code is safer typed than spoken.
Can I review from the terminal?
Yes, with the GitHub CLI. gh pr review 123 --comment -b "..." leaves a review comment, -r requests changes and -a approves. -F - reads the body from standard input.
Does dictating reviews send our code anywhere?
FnFlow only hears your voice and recognizes it on your Mac. The comment goes to GitHub when you submit it, like any typed comment.
Local Wispr Flow alternativeFnFlow vs VoiceInkVoice input for CursorHow 7 Mac dictation apps get you to your first dictationWhisper.cpp on Apple Silicon: which large-v3-turbo quantization to shipHow I built a local dictation appVoice dictation in Claude Code and the terminalWhy holding fn doesn't work for dictation on Mac (and how to fix it)How to run Whisper locally on an Apple Silicon MacSpokenly alternative for developersFnFlow vs EnviousWisprHow to dictate a good prompt for AI coding toolsVoice dictation in VS Code on a MacTeaching Whisper your jargon: initial prompt and replacementsWhy Whisper types "Thank you" on silence, and how to filter itPrivate dictation on a Mac at work: what actually leaves your machineVoice input for Codex CLI and the ChatGPT appVoice coding on a Mac: what actually worksWriting git commit messages by voiceDictation in IntelliJ IDEA, PyCharm and WebStorm on a MacDictation in Zed on a MacDictation in Terminal, iTerm2 and WarpWhich Whisper model to use on an Apple Silicon MacPush-to-talk dictation on a Mac: hold, toggle or streamSuperwhisper alternative for developersClaude Code voice mode: how to enable /voice and fix itWhisper apps: five ways to run Whisper locallyTalon voice coding vs a dictation appPush to talk on a MacDoes Claude have a voice mode?VoiceInk vs Wispr FlowVoiceInk vs SuperwhisperParakeet vs Whisper on a MacApple SpeechAnalyzer vs WhisperWhisper.cpp vs faster-whisper on a MacMlx-whisper vs whisper.cppGitHub Copilot voice inputGemini CLI voice inputVoice input in Google AntigravityVibe coding with voice input