// Draft a CHANGELOG.md entry for the current changes in Keep a Changelog format. Use when releasing, tagging a version, or updating CHANGELOG.md.
Explains code in plain language for someone unfamiliar with the programming language. Use when asked to explain code, walk through logic, describe what a function does, or when the user says "explain this" or "walk me through this".
Summarizes uncommitted git changes in a concise machine-readable format. Use in CI pipelines, scripts, or headless invocations where the output will be piped or captured.
Explains what a skill is and demonstrates that skills are working. Use when testing skills, when asked about skills, or when asked to demonstrate how skills work.
Demonstrates the personal scope for Claude Code skills. Use when testing personal-scoped skills or when the user wants to understand the difference between personal and project skill scopes.
Lists the conventions for this project and demonstrates the project scope for Claude Code skills. Use when asked about project conventions, code style, or as a demonstration of project-scoped skills.
Review code against a standard checklist covering security, correctness, performance, and readability. Use when asked to review code, check a PR, or audit changes.
| title | changelog-entry |
| name | changelog-entry |
| description | Draft a CHANGELOG.md entry for the current changes in Keep a Changelog format. Use when releasing, tagging a version, or updating CHANGELOG.md. |
| allowed-tools | Bash(git log *) Bash(git diff *) |
Find the most recent git tag:
git describe --tags --abbrev=0
If a tag exists, list commits since that tag:
git log --oneline --no-merges <last-tag>..HEAD
If no tag exists (the repository has no releases yet), list all commits:
git log --oneline --no-merges
Read each commit subject line and classify it into one of the Keep a Changelog sections:
Ignore merge commits, version bump commits, and changelog update commits. Ignore commits whose subject line is obviously tooling noise (dependency lock file updates with no semantic change, CI config tweaks that do not affect users).
Write the entry in Keep a Changelog format:
## [Unreleased]
### Added
- Description of added thing
### Changed
- Description of change
### Fixed
- Description of fix
Omit sections that have no entries.
Write each bullet in present tense, starting with a verb: "Add", "Fix", "Remove", "Update". Do not start bullets with the commit type prefix (feat:, fix:, etc.) — strip those and rephrase.
Output only the new CHANGELOG block. Do not output any surrounding explanation.