Voice for Code Reviews

Dictate thoughtful code review feedback instead of typing terse comments. Deliver clear, constructive suggestions that help your teammates improve.

The Problem

Code reviews suffer from two extremes: reviewers either leave cryptic one-liners that don't explain the reasoning, or they spend 20 minutes crafting detailed feedback for a single comment. Both waste time and create friction. Thoughtful reviews are essential but exhausting to type.

The Solution

Ummless lets you speak your code review feedback naturally, explaining your reasoning as if you were pair programming. The Code Review preset structures your thoughts into clear, constructive comments with context, suggestions, and rationale.

Workflow

Read the code change
Review the pull request diff in your browser or editor to understand the changes.
Open Ummless
Press Cmd+Shift+Space and select the Code Review preset.
Speak your feedback
Talk through your review as if explaining it to the author in person. Cover what you see, why it matters, and what you'd suggest.
Review the output
The preset formats your spoken feedback into a structured review comment with clear problem statements and suggestions.
Post the review
Paste the refined comment into the PR review interface on GitHub, GitLab, or your code review tool.

Before & After

Raw Transcript

So this function here, the uh processPayment one, it's catching all errors with a generic catch block and just logging them, which is um not great because if the Stripe API throws a rate limit error we should probably retry, and if it throws an invalid card error we should tell the user, but right now everything just gets swallowed into the same error handler.

Refined Output

The `processPayment` function uses a generic catch block that logs all errors identically. This means rate-limit errors from Stripe (which should trigger a retry) and invalid card errors (which should surface a user-facing message) are handled the same way. **Suggestion:** Consider differentiating error types in the catch block. Handle `RateLimitError` with exponential backoff retry logic, surface `CardError` to the user via the error response, and only log unexpected errors to your monitoring service.

Suggested Presets

Code Review

Frequently Asked Questions

Can I review multiple files in one session?

Yes. You can dictate feedback for multiple files or hunks in a single session. Just clearly state which file or function you're referring to as you speak.

Does it support inline code formatting?

The Code Review preset automatically wraps function names, variable names, and code references in backtick formatting when it detects them in your speech.

How do I keep feedback constructive?

The Code Review preset is tuned to present feedback constructively. It reframes criticism as suggestions and includes rationale. Speaking your reasoning naturally tends to produce more empathetic reviews than typing.

Ready to try it?

Download Ummless and start using voice for your workflow.