Voice Typing in GitHub

Why Voice Type in GitHub?

GitHub is where software gets built. But while the code itself is typed character by character in an editor, a surprising amount of a developer's GitHub time is spent writing prose — issue descriptions, pull request bodies, code review comments, discussion threads, and README documentation. This writing is critical to collaboration, yet it is often treated as an afterthought because typing it out is tedious.

The consequences are real. Vague issue descriptions lead to wasted implementation time. Sparse pull request bodies make reviews harder. Terse code review comments come across as unhelpful or dismissive. The common thread is that writing thorough prose by keyboard takes effort, and when developers are deep in code, that effort feels like friction.

Steno removes the friction. Hold a hotkey, speak your issue description or review comment naturally, release. Your words appear in the GitHub text field within a second at 130 to 150 words per minute. When writing detailed GitHub content takes seconds instead of minutes, the quality of your team's communication improves across the board.

Speaking at 130 to 150 WPM versus typing at 40 to 60 WPM means you can write a thorough pull request description in 20 seconds that would take a minute to type. Across dozens of PRs and issues per week, that time savings is significant. Check your own typing speed against speaking with our typing speed test.

How to Set Up Steno for GitHub

GitHub Workflows You Can Voice Type

Write Detailed Issue Descriptions

A well-written GitHub issue saves hours of back-and-forth. With Steno, you can dictate comprehensive issue descriptions that include context, expected behavior, actual behavior, and reproduction steps. Click on the issue body, hold the hotkey, and speak the full story. The natural flow of speech tends to include context that you would skip when typing, resulting in more complete and actionable issues.

Compose Pull Request Descriptions

Pull request descriptions explain what changed and why. Many developers leave the PR body blank or write a single line because typing a thorough description feels like a chore after finishing the code. With Steno, you can dictate a complete PR description in 30 seconds: what the change does, why it was needed, how it was implemented, and what reviewers should pay attention to. Use voice commands like "new line" to structure your description with clear sections.

Leave Thoughtful Code Review Comments

Code reviews are where teams maintain code quality and share knowledge. But typing detailed review comments is slow, so reviewers often leave short, cryptic notes like "Why?" or "Fix this." With Steno, you can hold the hotkey and speak a thorough explanation: "This function is doing two things — fetching the data and transforming it. I would suggest splitting it into two functions so they can be tested independently. The transformation logic is complex enough that unit tests would catch edge cases we might miss in integration tests." That kind of constructive feedback takes 15 seconds to speak but two minutes to type.

Contribute to Discussions

GitHub Discussions is where open source communities talk about ideas, ask questions, and make decisions. Meaningful participation requires writing thoughtful responses. Voice typing lets you contribute more actively because the effort of writing a long response drops to almost zero. Hold the hotkey, share your perspective, and release. Your contribution is ready to post in seconds.

Write Release Notes and Changelogs

When publishing a new release on GitHub, you need to write release notes that summarize what changed. This typically involves reviewing a list of merged PRs and writing a human-readable summary. With Steno, you can dictate release notes as you review each PR — hold the hotkey, say "Added support for dark mode theming across all components," release, and move to the next item. This turns a tedious documentation task into a quick voice dictation session.

Pro Tips for Voice Typing in GitHub

Frequently Asked Questions