Keep a Changelog Format
Standardizes project history by applying 'Keep a Changelog' principles and semantic versioning best practices to CHANGELOG.md files.
Standardizes project history by applying 'Keep a Changelog' principles and semantic versioning best practices to CHANGELOG.md files.
This skill empowers Claude to maintain professional, human-readable changelogs that adhere to the Keep a Changelog specification. It provides strict guidelines for categorizing updates into Added, Changed, Deprecated, Removed, Fixed, and Security sections, while enforcing an imperative writing style focused on user impact rather than internal implementation details. By using this skill, developers can automate the creation of high-quality release notes that seamlessly integrate with semantic versioning workflows, ensuring project histories are clear, linkable, and useful for both developers and end-users.