Voice for PR Descriptions

Dictate pull request descriptions that actually explain the changes. Help reviewers understand your code faster with well-written context and rationale.

The Problem

Pull request descriptions are either empty or copy-pasted from commit messages, leaving reviewers to reverse-engineer the intent from the diff. Writing a thorough PR description with context, motivation, and testing notes takes effort that feels redundant after you just wrote the code.

The Solution

Ummless lets you explain your PR out loud as if walking a reviewer through it. The Technical Documentation preset transforms your verbal walkthrough into a structured description with summary, motivation, changes made, and testing instructions.

Workflow

Finish your changes
Complete your code changes and push the branch to the remote.
Open Ummless
Press Cmd+Shift+Space and select "Technical Documentation."
Walk through the PR
Explain what you changed, why you changed it, how you tested it, and anything reviewers should pay attention to.
Review the description
Verify the output captures the key context and is structured for easy scanning.
Create the PR
Paste the description into GitHub, GitLab, or your platform's PR creation form.

Before & After

Raw Transcript

So this PR adds rate limiting to our API endpoints. We were getting hammered by like a few clients making way too many requests and it was affecting other users. I used a token bucket algorithm with Redis for the counter storage. I set it to 100 requests per minute per API key which should be plenty for normal usage. Oh and I added tests for the rate limiter middleware and updated the API docs.

Refined Output

## Summary Add rate limiting to API endpoints using a token bucket algorithm backed by Redis. ## Motivation A small number of clients were generating excessive request volume, degrading performance for other users. Rate limiting ensures fair usage across all API consumers. ## Changes - Implemented token bucket rate limiter middleware - Configured Redis as the counter store for distributed rate tracking - Set default limit to 100 requests/minute per API key - Added comprehensive tests for the rate limiter middleware - Updated API documentation with rate limit headers and error responses ## Testing - Unit tests for token bucket logic (fill rate, overflow, reset) - Integration tests verifying 429 responses when limits are exceeded - Manual testing with concurrent requests to confirm Redis counter accuracy

Suggested Presets

Technical Documentation

Frequently Asked Questions

Can I include testing instructions in the dictation?

Yes. Just mention how you tested the changes during your dictation. The preset will organize testing details into a separate section in the output.

Does it work for draft PRs too?

Absolutely. For draft PRs, you might mention what's still in progress. The preset will note work-in-progress items clearly in the description.

How detailed should I be?

Aim for 1-2 minutes of speaking. Cover the what, why, and how. The preset handles structuring; you just need to provide the content.

Ready to try it?

Download Ummless and start using voice for your workflow.