Write Commit Messages and PR Descriptions by Voice in the Terminal
Write clearer commit messages and PR descriptions by voice without leaving terminal context.
Speak the first version of a commit message or PR body, then clean up the wording before you save it.
What this looks like in practice
This page is about voice drafting for Git writing - not about generating commit structure for you automatically.
Example spoken draft
Conventional commit (single line)
feat(auth): add silent token refresh on 401 responsesWhere the value shows up
Commit messages and PR descriptions get drafted faster, while the final polish still happens directly in the text field or terminal editor.
Git writing demo slot
Ready for a future clip showing a spoken commit draft, a short edit pass, and the final saved message.
Supports future MP4, WebM, GIF/WebP, or poster-image fallback without changing the page layout.
How it works
Focus the terminal input
Place the cursor in the Claude Code, Codex CLI, or terminal input where the next line should go.
Press the hotkey and speak
Capture the first pass by voice instead of typing the whole prompt, command, or message from scratch.
PromptPaste transcribes locally
Speech is processed on-device on Windows and inserted directly into the active input field.
Refine before you send
Edit the draft at the cursor, then submit it when the wording and details look right.
The problem this solves
Commit messages get short and vague when typing them feels like an interruption to real work
PR descriptions are abbreviated or left template-incomplete because filling them out takes too long
Switching to a browser or external editor to write review notes breaks terminal flow
Multi-line git commit bodies are awkward to compose in a terminal prompt without a dedicated editor
Who this is for
Developers who use git CLI and write commit messages directly in the terminal
Engineers who write PR descriptions and review comments as part of a text-heavy workflow
Teams following conventional commits where message structure and rationale actually matter
Anyone who writes enough commit messages per day that the friction compounds
More example drafts
Conventional commit with body
feat(auth): add silent token refresh on 401 responses
When an access token expires, the client now silently requests a new token
using the stored refresh token before retrying the original request.
If the refresh fails, the user is redirected to the login page.
Refs: #892Bug fix commit with context
fix(cart): prevent null quantity on rapid add-then-remove
Adding an item and immediately removing it before state settled produced
a null quantity error in CartItem. Added a fallback to default quantity
to 1 when the value is undefined at render time.
Fixes: #1041Refactor commit
refactor(db): replace direct connections with connection pool
All database queries now go through a shared connection pool capped at
10 connections. Removes 6 direct pg.connect() calls. No API changes.Frequently asked questions
How do I dictate the conventional commit format without typing the colon and parentheses?
Dictate the message body naturally and manually type or edit the type prefix ('feat(auth):') in the terminal. The body content is what benefits most from voice.
Can I dictate a multi-line commit body?
Yes. Dictate the body naturally, then review and adjust spacing in the git editor before saving. Git commit editors accept multi-line input.
How do I write PR descriptions with PromptPaste?
It works with `gh pr create --body`, GitHub CLI editor mode, or any text field that accepts keyboard input - including the GitHub web interface.
How do I keep commit messages consistent with my team?
Pair PromptPaste with a `.gitmessage` commit template. Dictate into the template fields. Consistency comes from the template, not from typing.
Can this help with rebase commit messages?
Yes. PromptPaste works in any terminal input, including the editor opened during an interactive rebase.
Install PromptPaste and try this workflow on Windows
PromptPaste helps you speak a first draft, insert it directly at the cursor, and refine it in the terminal before you send it.
