domains / families / documents / changelog-entry
changelog-entry
authentic
Generate a properly formatted CHANGELOG.md entry in Keep a Changelog format from a commit range or PR. Groups changes into Added/Changed/Deprecated/Removed/Fixed/Security categories and outputs a ready-to-paste block.
When to use
- Before releasing a version: convert the commit log into a clean changelog entry.
- After merging a PR: document what changed for users and maintainers.
- When the user says "update changelog", "write changelog entry", "changelog for this release", or "what changed in v…".
When not to use
- The task is unrelated to changelogs or release notes.
- The user only wants a PR description (use `@git-pr-review` instead).
- The user only wants a commit message (use `@commit` instead).
- Relies on commit message quality; vague messages produce vague entries.
- Inspect public behavior and actual diff; do not invent CVEs, contributors, counts or release proof from commit subjects. Verify a provided tag/range and use documented empty-repository/no-tag behavior rather than choosing unrelated marketi…
- Does not write to CHANGELOG.md automatically — output is for manual review and paste.
- Stop and ask for clarification if the version number, date, or commit range is ambiguous.
Skill page
Source