changeloglisted
Install: claude install-skill Kuan-AI-com/agent-skills
# Changelog from commits
## 1. Fix the range
- User gave a range or versions: use it.
- Otherwise: `git describe --tags --abbrev=0` to get the last tag, range `<tag>..HEAD`.
- No tags at all: ask, or use the last CHANGELOG.md entry's date (`git log --since=<date>`). State the range you used at the top of your answer.
## 2. Collect, from the right source
- `git log <range> --no-merges --format='%h %s%n%b'` for the commits.
- If the repo squash-merges or merges PRs, PR titles carry the meaning: also read `git log <range> --merges --first-parent --format='%h %s'`.
- For any commit whose subject is vague ("fix", "wip", "updates") read `git show --stat <hash>` and the diff before classifying it. Do not guess from the message.
## 3. Detect breaking changes (check all, they are the most expensive to miss)
- `BREAKING CHANGE:` footer or `type!:` in Conventional Commits.
- Removed or renamed: public functions/exports, CLI flags, env vars, config keys, API endpoints or fields.
- Database migrations that drop/rename columns; changed defaults; raised minimum runtime versions.
Each breaking item needs a migration line: what the user must change, before -> after.
## 4. Classify by impact on the reader, not by commit type
Order: **Breaking changes**, **New**, **Improved**, **Fixed**, **Security** (if any), **Deprecated**.
Drop: refactors, CI, tests, formatting, dependency bumps with no user effect, reverted pairs (a commit and its revert cancel out). Keep a dependency bump only if it fi