Standardizes project changelogs using the Keep a Changelog specification and Semantic Versioning principles.
This skill empowers Claude to maintain high-quality, human-readable project documentation by enforcing the 'Keep a Changelog' standard. It provides structured guidance for categorizing updates into standardized groups—such as Added, Changed, and Fixed—while ensuring all entries are written with an imperative mood and a clear focus on user impact rather than technical implementation details. By integrating Semantic Versioning logic, the skill helps developers determine appropriate version bumps and maintain a linkable, reverse-chronological history of project evolution that is useful for both machines and humans.
Características Principales
01Categorizes updates into Added, Changed, Deprecated, Removed, Fixed, and Security buckets
02Enforces standardized 'Keep a Changelog' formatting and structure
031 GitHub stars
04Maps specific change categories to Semantic Versioning (SemVer) impact
05Standardizes entry writing style using imperative mood and user-centric language
06Automates the creation of linkable version headers and ISO-formatted release dates
Casos de Uso
01Maintaining an organized [Unreleased] section to track features for upcoming releases
02Auditing and refactoring existing changelogs to meet industry best practices
03Transforming technical git commit logs into professional, user-facing release notes
