# Changelog Generator

> Changelog Generator

- Skill: `comcclelland/changelog-generator` (Agent Skill)
- Install (CLI): `npx skillmds@latest add comcclelland/changelog-generator`
- Raw SKILL.md: https://api.skillmd.com/api/skills/comcclelland/changelog-generator/raw
- Safety review: pending (external: skill-scanner PASS, skillspector PASS)
- Works with: Claude Code, Claude.ai, OpenAI Codex
- Category: Coding & Dev Tools
- Author: comcclelland (https://skillmd.com/u/comcclelland)
- Updated: 2026-09-22
- Page: https://skillmd.com/skills/comcclelland/changelog-generator

---

# Changelog Generator

Generates release notes and changelogs from commit history.

## When to Use

- When the user asks to "generate a changelog", "write release notes", or "what changed since last release"
- Before tagging a release

## Process

1. Determine the range: last tag to HEAD, or user-specified range
   - `git tag --sort=-creatordate | head -1` to find last tag
   - `git log <last-tag>..HEAD --oneline` for commit list

2. Categorize commits by type (feat, fix, refactor, docs, chore, etc.)

3. Generate changelog in this format:

```markdown
## [version] — YYYY-MM-DD

### Added
- New features (from `feat` commits)

### Fixed
- Bug fixes (from `fix` commits)

### Changed
- Refactors, behavior changes (from `refactor` commits)

### Removed
- Removed features or deprecated items

### Infrastructure
- Build, CI, dependency changes (from `chore` commits)
```

### Rules
- Write entries from the user's perspective, not the developer's
- Combine related commits into single entries when they address the same feature/fix
- Skip trivial commits (typo fixes, formatting) unless they're the only changes
- Include breaking changes prominently at the top with migration instructions
- Link to PRs or issues when reference numbers are in commit messages

