Voice to Text for Commit Messages
Good commits explain why. Speaking that sentence is faster than staring at a one-line stub. Free to start.

The change is clear in your head for about two minutes after you finish. Then it becomes "fix stuff" forever.
Typing a careful message feels like a second task. Dictating keeps the bar high without stopping the merge train.
Open the commit box. Say what changed for the reader six months from now: problem, approach, anything risky.
If your team uses conventional commits, speak the type and scope first, then the sentence. Edit the subject line once with your eyes.
Commit spine:

Name the failure mode, not just the file you touched.

Say what users can do now that they could not before.

Call out behavior that should stay identical.

Impact and blast radius in one spoken paragraph.

Why the infra change exists so nobody reverts it blindly.

What broke and what you are rolling back to.
Use Voiskey in the IDE commit panel, gh CLI prompts you paste into, or the browser commit form. Same voice input wherever the message box lives.
Workflows around commits:
No. Speak enough for a future reader, then cut. One clear subject plus a short body beats a novel.
You say the type and scope; Voiskey types the words. You still own the final format before commit.
Dictate the prose, then paste or type trailer lines you keep as templates. Voice is for the human explanation.
Short commit messages barely dent a weekly word budget. Save heavier usage for PR bodies and docs.

Speak naturally, write effortlessly, and move faster. Turn your voice into polished, ready-to-use text wherever you work.
Use it across macOS, Windows, iOS, and Android