doncheli-changelog
Creates release notes and changelogs automatically by parsing conventional commit messages.
Install
mkdir -p .claude/skills/doncheli-changelog && curl -L -o skill.zip "https://agentskills.codes/api/skills/download/17787" && unzip -o skill.zip -d .claude/skills/doncheli-changelog && rm skill.zipInstalls to .claude/skills/doncheli-changelog
Activation
This is the description your AI agent reads to decide when to run this skill — the better it matches your request, the more reliably it fires.
Auto-generate CHANGELOG.md entries from git commit history. Activate when user mentions "changelog", "release notes", "what changed", "generate changelog", "CHANGELOG", "release history".Key capabilities
- →Determine commit range for changelog generation
- →Parse conventional commit prefixes from git log
- →Map commit types to Keep a Changelog categories
- →Extract short hash for traceability in each entry
- →Insert new changelog section at the top of `CHANGELOG.md`
- →Create `CHANGELOG.md` with standard header if it doesn't exist
How it works
The skill determines a commit range, parses git log for conventional commit prefixes, and maps them to changelog categories. It then inserts these new entries into `CHANGELOG.md`, creating the file if it doesn't exist.
Inputs & outputs
When to use doncheli-changelog
- →Generating release notes
- →Updating changelog files
- →Tracking project changes
About this skill
Don Cheli: Changelog Auto-Generator
Instructions
- Determine the commit range:
- Default: from the last semver tag to HEAD
- With
--from/--to: use the specified refs - With
--version: use that as the new version number
- Run
git log --oneline <range>and parse conventional commit prefixes - Map commit types to Keep a Changelog categories:
feat/feat!→ Added (breaking changes go in a separate top section)fix→ Fixedrefactor/perf→ Changeddocs→ Changedsecurity→ Securitydeprecated→ Deprecatedremove→ Removedtest/chore/ci→ omit by default (include with--verbose)
- Extract the short hash and append it to each entry for traceability
- Skip merge commits (
Merge branch,Merge pull request) - Insert the new section at the top of
CHANGELOG.md, below the header — never overwrite existing entries - If no
CHANGELOG.mdexists, create it with the standard Keep a Changelog header - With
--dry-run, print to stdout only — do not write to file - After writing, confirm with the user and suggest
git add CHANGELOG.md
Quality Gate
- If fewer than 2 commits are found in the range, warn the user before generating
- If breaking changes are detected (
feat!,BREAKING CHANGEfooter), highlight them prominently - Never infer a version number from non-semver tags — ask the user to provide
--version
When not to use it
- →When the user does not mention 'changelog' or 'release notes'
- →When the project does not follow conventional commit messages
- →When a specific version number is not provided for non-semver tags
Limitations
- →Relies on conventional commit prefixes for categorization
- →Requires a commit range or version number for generation
- →Does not infer version numbers from non-semver tags
How it compares
This skill automates changelog generation by directly parsing git commit history and categorizing changes based on conventional commit messages, providing a structured and traceable update to `CHANGELOG.md` rather than manual entry.
Compared to similar skills
doncheli-changelog side by side with the closest alternatives in the catalog.
| Skill | Installs | Updated | Safety | Difficulty |
|---|---|---|---|---|
| doncheli-changelog (this skill) | 0 | 4mo | Review | Intermediate |
| prepare-changelog | 6 | 6mo | Review | Beginner |
| workthrough | 10 | 8mo | Review | Beginner |
| generate-release-notes | 7 | 7mo | Review | Intermediate |
Try saying
Example prompts that trigger this skill in your AI assistant.
More by doncheli
View all by doncheli →You might also like
prepare-changelog
nextest-rs
Guidelines for preparing changelog entries for nextest releases following Keep a Changelog format
workthrough
bear2u
Automatically document all development work and code modifications in a structured workthrough format. Use this skill after completing any development task, bug fix, feature implementation, or code refactoring to create comprehensive documentation.
generate-release-notes
teambit
Generate comprehensive release notes for Bit from git commits and pull requests. Use when creating release notes, building changelogs, documenting version releases, or preparing a new Bit release.
changelog-generator
ComposioHQ
Automatically creates user-facing changelogs from git commits by analyzing commit history, categorizing changes, and transforming technical commits into clear, customer-friendly release notes. Turns hours of manual changelog writing into minutes of automated generation.
release-note-generation
microsoft
Toolkit for generating PowerToys release notes from GitHub milestone PRs or commit ranges. Use when asked to create release notes, summarize milestone PRs, generate changelog, prepare release documentation, request Copilot reviews for PRs, update README for a new release, manage PR milestones, or collect PRs between commits/tags. Supports PR collection by milestone or commit range, milestone assignment, grouping by label, summarization with external contributor attribution, and README version bumping.
doc-check
coder
Checks if code changes require documentation updates