bmad-os-changelog

Generating a changelog from git commit history involves analyzing merged pull requests and commit context to categorize changes into Features and Breaking Changes. This process automatically drafts structured release notes directly into your CHANGELOG.md.

Yes, automatically categorizing pull requests into release notes groups changes into standardized sections like Features, Breaking Changes, and Other. It analyzes PR metadata to provide meaningful summaries rather than raw commit messages.

Generating changelog entries requires access to your local git history and the project's CHANGELOG.md file. The skill performs non-destructive updates directly into this existing documentation.

The best way to format AI-generated release notes is applying a mandatory writing-quality pass to strip filler content. This ensures clear, concise communication while maintaining professional project history standards.

Automated changelogs contain filler text when lacking a strict writing-quality pass. Applying quality assurance standards during generation strips AI-generated filler to ensure clear, concise communication in your project documentation.

Limitations of non-destructive changelog updates include relying entirely on existing local git history and PR metadata accuracy. It updates the CHANGELOG.md file without overwriting previous entries but cannot invent missing context.