Changelog Writing

by samber98ed86da8babMIT2 starsListed Oct 8, 2026Updated Oct 8, 2026Repository updated 10 days ago

Turns raw commits, pull requests and tickets into release notes developers actually read - a scannable record of what shipped, what it means in practice, and what breaks. Use whenever the user mentions a changelog, CHANGELOG.md, release notes, a GitHub release body for a tag, a hosted "what's new" page, app-store release notes, Keep a Changelog, or Common Changelog, or asks what to write for a release they just cut - even when the commit history is messy and follows no commit convention. Not for version bumping, tagging or publishing pipelines. Do NOT use for a full breaking-change upgrade guide - use samber/developer-relations-skills@version-migration-guide; for a narrative release post use samber/developer-relations-skills@engineering-blog-post.

  1. 98ed86da8babCurrentcommit 98ed86dPublished Oct 8, 2026

Source and attribution

Source:samber/developer-relations-skillsinskills/changelog-writingat commit98ed86d

License: MIT

Content belongs to its original authors. SourceWeft indexes it from a public repository.

Report or request removal