changelog-generator
Generates user-facing changelogs and release notes from git commit history. Parses conventional commits, categorizes changes into features, fixes, breaking changes, and more, then rewrites technical messages into customer-friendly language. Use when the user asks to generate a changelog, write release notes, summarize recent commits, prepare CHANGELOG.md, or document what changed between versions.
npx skills add ECNU-ICALK/AutoSkill --skill changelog-generator --agent claude-code
Same command for any agent — swap --agent for codex, cursor, copilot.
Weekly change comes from our own snapshots, not the repository page — it measures attention, not adoption.
# Changelog Generator Generate structured, user-facing changelogs from git commit history. ## Workflow ### Step 1 — Gather commits Determine the commit range from the user's request, then fetch commits: ```bash # Between tags/versions git log v1.2.0..v1.3.0 --oneline --no-merges # Since a date git log --since="2024-03-01" --oneline --no-merges # Since last tag (default when no range given) git log "$(git describe --tags --abbrev=0)"..HEAD --oneline --no-merges ``` If there are no tags and no range specified, ask the user for a date or count. ### Step 2 — Categorize each commit Apply these rules based on the commit message prefix: | Prefix / pattern | Category | |---|---| | `feat:` `feature:` | New Features | | `fix:` `bugfix:` | Bug Fixes | | `perf:` | Performance | | `BREAKING CHANGE` or `!:` suffix | Breaking Changes | | `security:` `vuln:` | Security | | `docs:` `test:` `ci:` `chore:` `refactor:` `style:` `build:` | Skip (internal) | For non-conventional messages, infer category from content. Exclude purely internal commits (test infra, CI config, linting, dependency bumps with no user impact). ### Step 3 — Rewrite for a non-technical audience Transform each kept commit into a c
- Workflow
- Step 1 — Gather commits
- Step 2 — Categorize each commit
- Step 3 — Rewrite for a non-technical audience
- Step 4 — Format the output
- Step 5 — Validate before presenting
Between tags/versions git log v1.2.0..v1.3.0 --oneline --no-merges Since a date git log --since="2024-03-01" --oneline --no-merges Since last tag (default when no range given) git log "$(git describe --tags --abbrev=0)"..HEAD --oneline --no-merges
What does the changelog-generator skill do?
Generates user-facing changelogs and release notes from git commit history. Parses conventional commits, categorizes changes into features, fixes, breaking changes, and more, then rewrites technical messages into customer-friendly language. Use when the user asks to generate a changelog, write release notes, summarize recent commits, prepare CHANGELOG.md, or document what changed between versions.
How do I install it?
Run `npx skills add ECNU-ICALK/AutoSkill --skill changelog-generator --agent claude-code` — it drops the skill into your project so the agent can pick it up. Swap the --agent value for codex, cursor or copilot if you use one of those.
Where does this skill come from?
From ECNU-ICALK/AutoSkill, a repository with 539 stars. We read it straight from the repository tree rather than a submitted listing, so what you see here is what is actually published.
Is a popular skill a good skill?
Not necessarily. Stars measure attention, not adoption — a repository can trend for a week and be abandoned. That is why we show the weekly change from our own snapshots next to the total, instead of a single flattering number.