Voice to Text for GitHub Issues
Open GitHub Issues That Strangers Can Act On
Vague issues bounce. Speak problem, repro, and acceptance criteria into Voiskey at the cursor. Free to start.
Why Issues Bounce
Maintainers cannot guess your environment. Contributors cannot guess done. Typing a careful issue feels like unpaid work—so it stays thin.
Dictating while the failure is on screen is faster than writing from memory after dinner.
An Issue Spine You Can Speak
Problem, version, steps, expected, actual, and what good looks like. Link related PRs after.
GitHub issue spine:
- Problem in one sentence
- Version and environment
- Repro steps
- Expected vs actual
- Acceptance criteria
Issues Worth Dictating
Bug Reports
Repro while the stack trace is still open.
Feature Requests
User story and non-goals without a manifesto.
Good First Issues
Scope a bite-sized task newcomers can finish.
RFC Tracking Issues
Link the debate and name remaining questions.
Upstream Reports
Minimal repro for maintainers outside your company.
Release Blockers
Impact and workaround for triage speed.
Dictate in github.com or the IDE
Use Voiskey in the issue form, comment box, or GitHub in VS Code. Add project names to vocabulary so they land clean.
Workflows around issues:
- Issue body draftsVoice typing for notes
- Issue comment threadsVoice typing for messages
- Maintainer email follow-upsVoice typing for emails
- Team triage summariesVoice typing for teams
- Triage meeting notesVoice typing for meetings
FAQ s
Yes. Move through each section and speak under the headings your repo already defines.
Paste error output. Dictate the human explanation around it.
Yes. Internal issues suffer the same vagueness problem—and the same fix.
No. It only produces text. You still set metadata in GitHub.
VoiskeyYour voice, amplified.
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