Automate Changelog Generation and Versioning

This is a skill for automating changelog generation, release notes, and version management following industry standards - conventional commits, standardized commit message formats, and semantic versioning. Its workflow: select a changelog format and versioning strategy, enforce commit conventions or labeling rules, configure tooling to generate and publish notes, and review the output for accuracy, completeness, and wording. Detailed patterns, templates, and examples live in a companion resources/implementation-playbook.md file.

Use this skill when setting up automated changelog generation, implementing conventional commits, creating release-note workflows, standardizing commit message formats, or managing semantic versioning. Don't use it if the project has no release process or versioning, if you only need a one-time manual release note, or if the commit history is unavailable or unreliable. It carries an explicit safety constraint: avoid exposing secrets or internal-only details in release notes.

Input is a project's commit history and versioning strategy; output is an automated changelog and release-note pipeline - enforced commit conventions, generated and published notes, and semantic version bumps - with detailed patterns available in the companion playbook file.

Engineering teams setting up or standardizing automated changelog and release-note generation who want conventional commits and semantic versioning enforced consistently, rather than writing release notes manually each time.