changelog-generator

Run the changelog generator from your repository root and specify a scope such as commits since the last release, a date range, or a version tag. It analyzes the commit history, categorizes changes, and outputs formatted Markdown release notes.

Translate technical commit messages into outcome-focused language describing what users gain, not what code changed. Group entries into features, improvements, and fixes, and filter out internal work like refactoring and test updates.

Yes, you can scope generation to commits between two dates, since a specific version tag like v2.4.0, or a relative period such as the past week. Narrower ranges produce more focused changelogs.

Yes, you can point it to a style file such as CHANGELOG_STYLE.md and it will apply your formatting conventions and brand voice to the generated entries. Review the output before publishing to confirm tone consistency.

Internal commits such as refactoring, test changes, and other developer-only noise are filtered out automatically. Only changes meaningful to end users appear in the final categorized output.