Menu
Writes a Keep a Changelog entry from a description of changes or a git log. Use when the user asks for a changelog entry, release notes, or mentions updating CHANGELOG.md.
Install with Codex or Claude Copy this prompt, paste it into Codex, Claude, or another assistant, and let it review the skill page and install it for you.
Based on SOC occupation classification
Writes a single Conventional Commits message from a description of changes or a git diff. Use when the user asks for a commit message, or mentions committing, staging, or a diff.
Counts the non-blank lines in a file using the bundled count.py script. Use when asked for an exact line count of a file, where guessing is unacceptable.
Reviews a diff or file for bugs, security issues, and missing tests, returning prioritized findings. Use when the user asks for a code review, a PR review, or "what's wrong with this code".
| name | writing-changelog |
| description | Writes a Keep a Changelog entry from a description of changes or a git log. Use when the user asks for a changelog entry, release notes, or mentions updating CHANGELOG.md. |
Produce a Keep a Changelog entry for the changes described. Write for a human reader deciding whether to upgrade — lead with impact, not implementation.
Added, Changed, Deprecated, Removed, Fixed, Security.(#123) when given. No author handles, no dates
inside bullets.## [<version>] - <YYYY-MM-DD>
### Added
- <new capability and why it matters> (#NN)
### Fixed
- <the bug, stated as the symptom the user saw> (#NN)
Output only the entry. If a version or date is unknown, use [Unreleased] and
omit the date.