Release notes from the Git history you choose

Changelog Generator turns a local Git revision range, recent commit window, or tag comparison into plain Markdown release notes. It keeps every commit visible, detects breaking markers, suggests the next SemVer bump, and never publishes or changes the repository.

What v1.3 does

• Flexible ranges: Use an explicit two-dot range, the last N commits, the newest two tags, or the nearest reachable tag to HEAD. Tagless repositories fall back transparently to the last 20 commits.
• Tolerant grouping: Groups feat, fix, docs, style, refactor, test/tests, and chore commits. Unknown, empty, merge-like, revert-like, and malformed subjects remain visible under Chores.
• Breaking-change detection: Recognizes ! in Conventional Commit headers plus both BREAKING CHANGE: and BREAKING-CHANGE: footer spellings.
• Auditable output: Produces portable UTF-8 Markdown with short commit hashes, plain headings, a range summary, and a reviewable SemVer suggestion.
• Safer commit text: Neutralizes terminal and invisible formatting controls from untrusted commit messages.

Local and read-only by design

The included Python helper reads local Git commit metadata only. It does not fetch, pull, push, tag, commit, publish, inspect diffs or repository files, read credentials or environment variables, or use the network. Output is written only when you explicitly provide an output path.

Known limitations

• The SemVer result is a suggestion. Maintainers still decide compatibility and release policy.
• Commit labels can be missing or wrong; custom commit types are retained under Chores.
• The skill does not infer changes from diffs, generate GitHub releases, or modify CHANGELOG.md unless you explicitly request an output file.