Changelog

Skill huzaifa525/claude-code-optimizer/templates/.claude/skills/changelog

Optimize Claude Code token usage — 22 skills, 8 hooks, 6 rules. One npm install. Zero manual steps. Cut costs by 67%.

Install

npx -y skills add huzaifa525/claude-code-optimizer --skill changelog

Assembled from the repository path, not quoted from the project. Check it against their README if it does not work.

One thing to look at

9 stars9 stars. Stars are a popularity signal and not a quality one, but at this level it is likely that nobody has read this closely except its author, and you would be relying on your own review.

What its author says it does

Copied from the file, not written here

Use when the user wants a changelog, release notes, or asks what changed since the last release.

SKILL.md

1.5 KB, as published. Nobody here has run it

Generate a changelog from git history.

Steps

Find the last tag

git describe --tags --abbrev=0 2>/dev/null || echo "no-tags"

Get commits since last tag
```
git log [last-tag]..HEAD --oneline --no-merges
```
If no tags, get last 50 commits.

Categorize commits by prefix:

Category	Prefixes
Features	feat:, feature:, add:
Bug Fixes	fix:, bugfix:, hotfix:
Performance	perf:
Refactoring	refactor:
Documentation	docs:, doc:
Testing	test:, tests:
CI/CD	ci:, cd:, build:
Chores	chore:, deps:, bump:
Breaking Changes	any commit with BREAKING CHANGE in body

If commits don't use conventional prefixes, categorize by content.

Generate CHANGELOG.md entry:

## [version] - YYYY-MM-DD

### Features
- Description ([commit-hash])

### Bug Fixes
- Description ([commit-hash])

### Performance
- Description ([commit-hash])

### Breaking Changes
- Description ([commit-hash])

If CHANGELOG.md exists, prepend the new entry at the top (after the title). If it doesn't exist, create it.
Show the generated changelog to the user.

One thing to look at

What its author says it does

SKILL.md

Steps

Keep looking