Voice to Text for Bitbucket
Bitbucket keeps your code organized, but explaining that code takes forever. PR descriptions, code review comments, issue tracking, wiki documentation. All the writing that surrounds your commits. Blurt lets you speak it instead of typing it. Hold a button, explain your changes naturally, release. Text appears in Bitbucket wherever your cursor is. Your PRs get the context they need. Your code reviews become genuinely helpful. Your issues get documented in seconds, not minutes.
The Typing Problem
PR descriptions get skipped because typing takes too long
You just finished a complex feature across multiple files. Now Bitbucket wants you to describe what you did. You could explain it verbally in 30 seconds, but typing a proper description takes 10 minutes. So you write 'Updates' and hit create. Your reviewers open the PR with zero context. The review drags on with unnecessary back-and-forth questions.
Code review comments are either too brief or too time-consuming
You found a potential issue in a colleague's PR. You know exactly what the problem is and how to solve it. But writing a clear, constructive explanation takes effort. You're tempted to just write 'fix this' but that's not helpful. So you either spend 5 minutes crafting a thoughtful response, or you leave something vague. Neither option feels right.
Jira-linked issues need context but you're out of energy
Your team uses Bitbucket with Jira integration. Every issue needs proper descriptions, acceptance criteria, and technical details. After a day of coding, writing detailed issue descriptions feels like homework. The issues pile up with minimal context. Sprint planning becomes a guessing game.
Wiki pages stay empty because documentation is a chore
The Bitbucket wiki should have setup guides, architecture docs, and onboarding information. Everyone agrees it's important. Nobody wants to write it. After hours of coding, more typing is the last thing anyone wants. So the wiki remains a ghost town. New team members struggle. Knowledge stays locked in people's heads.
Repository descriptions and README files are always outdated
Your repositories need current documentation. The README should explain how to get started. The repo description should say what this project does. But updating these takes time, and there's always more urgent work. So they stay stale. New developers get confused. Onboarding takes longer than it should.
How It Works
Blurt works everywhere in Bitbucket. PR descriptions, code review comments, issue descriptions, wiki edits, README updates. If you can type it, you can speak it.
Hold your hotkey
Press your chosen shortcut while your cursor is in any Bitbucket text field. A small indicator shows Blurt is listening.
Explain naturally
Describe your changes, explain your reasoning, document the approach. Talk like you're explaining to a teammate. Blurt handles punctuation automatically.
Release and done
Text appears in Bitbucket. Edit if needed, or submit directly. Your thoughts become documentation in seconds, not minutes.
Real Scenarios
Writing PR descriptions that give reviewers real context
Your PR is ready for review. Hold the button and explain: 'This refactors the payment processing module to support multiple currency types. The main changes are in the payment controller and the currency converter service. I added validation for currency codes and updated the API response format. Testing notes: use the test merchant account in staging. The exchange rates are mocked for consistency.' A description that would take 5 minutes to type takes 30 seconds to speak. Reviewers know exactly what they're looking at.
Constructive code review feedback without the time drain
You spotted a SQL injection risk in someone's PR. Hold and explain: 'This query concatenates user input directly into the SQL string, which creates an injection vulnerability. Consider using parameterized queries instead. We have a query builder utility in the database helpers folder that handles this pattern. I can point you to an example if helpful.' Detailed, actionable feedback in 15 seconds. You identified the problem, explained the risk, and offered a solution path.
Issue descriptions that actually help during implementation
You need to create an issue for a bug you discovered. Hold and document: 'When a user submits a form with special characters in the name field, the server returns a 500 error. This happens because the input sanitization runs after the database insert instead of before. Reproduction steps: create a new user with an ampersand in the name. Expected behavior: form should accept valid special characters. Suggested fix: move sanitization to the request validation layer.' Complete issue documentation in 20 seconds.
Wiki pages that actually get written and maintained
The team needs a deployment guide in the wiki. Hold and explain the process: 'First, ensure all tests pass on the main branch. Then run the build script with the production flag. The output goes to the dist folder. Upload the contents to the CDN using the deployment CLI. Finally, update the version tag in the release tracker. Rollback procedure: redeploy the previous tagged version using the same steps.' A wiki page that would sit in your backlog for weeks gets done in one minute.
Inline code comments that explain the why, not just the what
Your PR has a complex algorithm that needs explanation. Hold and add context: 'This sorting approach looks unusual but it is intentional. The standard library sort is not stable for this data type in older Node versions, so we use a custom comparator that preserves insertion order. See the related issue in the Node.js repository for background.' Future maintainers will thank you.
Responding to PR feedback quickly and thoroughly
A reviewer asked why you chose a particular approach. Hold and respond: 'Good question. I considered using the existing caching layer, but it does not support TTL-based invalidation which we need for this feature. The new approach adds minimal overhead and gives us more control over cache eviction. I benchmarked both approaches and this one is actually faster for our typical payload sizes.' Thoughtful responses without the typing fatigue.
Repository descriptions that help developers find what they need
Your team has dozens of repositories in Bitbucket. Each one needs a clear description. Hold and describe: 'This repository contains the customer notification service. It handles email, SMS, and push notifications for the main application. Depends on the messaging queue and the template service. See the wiki for configuration options.' Every repo gets a useful description without hours of documentation work.
Why Bitbucket users choose Blurt over built-in dictation
| Blurt | macOS Dictation | |
|---|---|---|
| Activation | Single hotkey, instant start | Click microphone or double-tap function key |
| Speed | Text appears in under 500ms | 2-3 second delay before transcription |
| Technical terms | Handles Atlassian jargon well (Jira, Confluence, pipeline) | Often mishears technical vocabulary |
| Reliability | Consistent accuracy in browser text fields | Sometimes fails in web apps |
| Price | $10/month or $99/year, free tier included | Free but limited |
Frequently Asked Questions
Start Typing Faster Today
Free to try — no credit card required
Download Blurt