update-release-notes

To generate Flutter release notes from git commits, the skill scans recent commit history and diffs touching lib/, android/, ios/, or pubspec.yaml, then writes user-facing changes into the Unreleased section of release_notes.txt.

Yes, you can automatically update your changelog while excluding internal changes. The skill inspects commit diffs and skips purely internal, test, CI, or dependency-only commits to produce only user-facing release notes.

Yes, the release notes generator preserves existing entries in the Unreleased section. It compares new user-facing changes against existing lines to avoid duplicates and only appends new items to the file.

You prepare a Flutter app changelog by asking the skill to scan a specified number of recent commits, which then identifies visible user-facing changes and updates release_notes.txt locally without running git commit or git push.

A key limitation when automating release notes from commit diffs is that the skill edits release_notes.txt locally but does not run git commit or git push, requiring you to manually version control the updated changelog.