~/.claude/skills/changelog-writer/SKILL.mdChangelog Writer
Reads git history and generates a human-readable changelog grouped by feature, fix, and breaking change.
--- name: changelog-writer description: | Generates a changelog from git history grouped by type of change. IMPORTANT: Activate this skill whenever the user asks to "write a changelog", "generate changelog", "what changed", or "release notes". This skill MUST be used for all changelog generation requests. --- # Changelog Writer Reads your git commit history and generates a clean, human-readable changelog. Groups changes by type (features, fixes, breaking changes) and writes description
Reads your git commit history and generates a clean, human-readable changelog. Groups changes by type (features, fixes, breaking changes) and writes descriptions that make sense to users.
Say any of these to activate this skill: - "write a changelog" - "generate changelog" - "what changed since [version/date]" - "Use skill: changelog writer"
1. Read the git log since the last tag, release, or specified date 2. Parse commit messages and categorize: feature, fix, refactor, docs, breaking change 3. For conventional commits (feat:, fix:, etc.), use the prefix for categorization 4. For non-conventional commits, read the message and diff to determine the category 5. Group changes by category and write human-readable descriptions 6. Highlight breaking changes prominently at the top 7. Include the date range and commit count
- Write for END USERS, not developers (unless it's a library)
- "Added dark mode support" is better than "feat: add ThemeProvider and dark class toggle"
- Group related commits into a single changelog entry
- Always highlight breaking changes with a clear migration note
- Skip internal refactors and CI changes unless they affect users
- Best with: Claude Code CLI (can read git history directly)
- Also works: Cursor, Windsurf (share git log output)
- Expects: A git repository with commit history
- Markdown changelog with: version/date header, breaking changes, features, fixes
- Each entry is one sentence describing the user-visible change