prepare-changelog

Keep a Changelog is a standardized format for documenting changes across software releases. It organizes entries into sections—Added, Changed, Fixed, Deprecated, Removed, Security—making release notes scannable, consistent, and user-focused. This format helps users quickly find what changed between versions.

Create a version header with the release date, then organize changes into semantic sections: Added, Changed, Fixed, Deprecated, Removed, Security, and Known issues. Write each bullet in present tense, user-facing language with supporting links. Include contributor attribution and forward-looking notes to provide context and clarity.

Good entries are concise, present-tense bullets that explain what changed and why it matters to users, supported by relevant links. Poor entries are vague, internal-focused, or lack motivation. Enforce Markdown structure, clarity, and consistency so readers understand the impact of each change without guessing.

Keep a Changelog is designed for versioned software releases and works best when changes map to semantic version increments. It's less suited for continuous or non-versioned documentation. The format assumes discrete release cycles with distinct, user-visible changes to communicate.

No. Keep a Changelog is a plain-text Markdown convention, so any text editor works. You need only consistent discipline: following the section structure, present-tense voice, and linking guidelines. The Skill enforces these standards through documented guidelines, not tooling requirements.