changelog▌

Create comprehensive API changelogs that document changes, deprecations, breaking changes, and provide migration guides for API consumers.

$22

Changelogs and release notes that users actually read and act on. \n \n Covers entry structure, user-facing language, and categorization (New, Improved, Fixed, Removed, Security) with clear rules for when to use each \n Includes semantic and date-based versioning strategies, visual changelog guidance, and templates for breaking changes with migration timelines \n Provides distribution channel recommendations (changelog page, in-app, email, blog, social) and writing best practices to avoid common

Automatically transforms git commits into polished, customer-friendly release notes. \n \n Analyzes commit history within specified date ranges or between versions, then categorizes changes into features, improvements, bug fixes, breaking changes, and security updates \n Converts technical commit messages into clear, user-facing language while filtering out internal noise like refactoring and test commits \n Supports custom changelog style guidelines via CHANGELOG_STYLE.md for consistent formatt

Automate changelog generation from commits following Conventional Commits and Keep a Changelog standards. \n \n Supports multiple implementation methods: Conventional Changelog (Node.js), standard-version, semantic-release with full CI/CD automation, git-cliff (Rust-based), and commitizen (Python) \n Enforces Conventional Commits format with commitlint validation, mapping commit types (feat, fix, perf, etc.) to changelog sections automatically \n Includes semantic versioning integration, GitHub