Voice for Changelogs
Dictate changelog entries after each release instead of writing them from memory. Capture what changed, what was fixed, and what was removed accurately.
The Problem
Changelogs are either neglected entirely or written in a last-minute rush before release, leading to incomplete or inaccurate entries. Writing them from git logs is tedious, and important user-facing changes get buried or missed.
The Solution
Ummless lets you dictate changelog entries as you complete features and fixes throughout the development cycle. The Quick Cleanup preset formats your notes into clean, user-friendly changelog entries categorized by type.
Workflow
- Complete a feature or fix
After finishing a meaningful change, open Ummless immediately.
- Select Quick Cleanup
Choose "Quick Cleanup" for concise, polished output.
- Describe the change
Explain what you added, changed, fixed, or removed from the user's perspective. Focus on impact, not implementation.
- Categorize and save
Review the output, tag it as Added/Changed/Fixed/Removed, and add it to your running changelog draft.
Before & After
Raw Transcript
Refined Output
Suggested Presets
Frequently Asked Questions
Does it follow Keep a Changelog format?
The Quick Cleanup preset produces clean categorized entries. For strict Keep a Changelog formatting, create a custom preset with those specific conventions.
Should I dictate per-feature or per-release?
Per-feature is recommended. Dictate a quick entry after each meaningful change and compile them at release time. This ensures nothing is forgotten.
How do I handle breaking changes?
Mention that a change is breaking during your dictation. The output will clearly flag it. Consider adding a custom preset category for breaking changes.
Related Content
Voice for Commit Messages
Speak your commit messages to write meaningful git history. Stop settling for 'fix stuff' when you can effortlessly describe what changed and why.
Use CaseVoice for PR Descriptions
Dictate pull request descriptions that actually explain the changes. Help reviewers understand your code faster with well-written context and rationale.