changelogator
Generate a changelog from git commits. Use when the user asks to generate a changelog, prepare release notes, summarize commits, prepare a release, suggest a version bump, or review changes since last tag. Also use when the user mentions "changelog", "release notes", "what changed", "version bump", or "semver".
Best use case
changelogator is best used when you need a repeatable AI agent workflow instead of a one-off prompt.
Generate a changelog from git commits. Use when the user asks to generate a changelog, prepare release notes, summarize commits, prepare a release, suggest a version bump, or review changes since last tag. Also use when the user mentions "changelog", "release notes", "what changed", "version bump", or "semver".
Teams using changelogator should expect a more consistent output, faster repeated execution, less prompt rewriting.
When to use this skill
- You want a reusable workflow that can be run more than once with consistent structure.
When not to use this skill
- You only need a quick one-off answer and do not need a reusable workflow.
- You cannot install or maintain the underlying files, dependencies, or repository context.
Installation
Claude Code / Cursor / Codex
Manual Installation
- Download SKILL.md from GitHub
- Place it in
.claude/skills/changelogator/SKILL.mdinside your project - Restart your AI agent — it will auto-discover the skill
How changelogator Compares
| Feature / Agent | changelogator | Standard Approach |
|---|---|---|
| Platform Support | Not specified | Limited / Varies |
| Context Awareness | High | Baseline |
| Installation Complexity | Unknown | N/A |
Frequently Asked Questions
What does this skill do?
Generate a changelog from git commits. Use when the user asks to generate a changelog, prepare release notes, summarize commits, prepare a release, suggest a version bump, or review changes since last tag. Also use when the user mentions "changelog", "release notes", "what changed", "version bump", or "semver".
Where can I find the source code?
You can find the source code on GitHub using the link provided at the top of the page.
SKILL.md Source
# Changelogator Generate a structured changelog from git commits following [Keep a Changelog](https://keepachangelog.com/) format. **By default**, output the changelog in chat for the user to review — do **not** write to `CHANGELOG.md` unless the user explicitly asks. ## Workflow 1. **Find the last tag**: `git tag --sort=-v:refname | head -1` 2. **Retrieve commits**: `git log <tag>..HEAD --format="---COMMIT---%n%H%n%s%n%b" --reverse` (if no tag, use `git log --format="---COMMIT---%n%H%n%s%n%b" --reverse`) 3. **Parse** each commit subject using the format below 4. **Classify** into changelog categories using the mapping table 5. **Detect breaking changes**: `!` after type (e.g., `feat!`) or `BREAKING CHANGE` in body 6. **Suggest semver bump** based on the rules below 7. **Generate** the markdown changelog 8. **Output in chat** for validation ## Commit Format Expected format (from commitor): ``` <emoji> <type>(<scope>): <description> (<TASK-XXX>) ``` Parse using these parts: - **Emoji**: leading Unicode emoji - **Type**: word after emoji (`feat`, `fix`, `patch`, etc.) - **Scope**: optional, inside parentheses after type - **Breaking**: `!` between type/scope and `:` - **Description**: text after `: ` - **Task number**: optional, inside parentheses at end of subject ## Category Mapping Map commit types to changelog categories (consistent with commitor): | Changelog Category | Emoji | Commit Types | | ------------------ | ----- | -------------------------------- | | Added | ✨ | feat | | Changed | 🔨 | patch, style, perf, data | | Fixed | 🐛 | fix | | Removed | 🔥 | remove | | Technical | ⚙️ | docs, refactor, test, ai, config | ## Semver Rules Suggest a version bump based on the most significant change: | Condition | Bump | | ----------------------------------- | ----- | | Any breaking change (`!` or body) | Major | | Any `feat` commit | Minor | | Everything else (fix, patch, etc.) | Patch | Apply to the last tag version. If no tag exists, suggest `v0.1.0`. ## Output Template ```markdown ## vX.Y.Z - YYYY-MM-DD ### ✨ Added - **scope**: description - description without scope ### 🔨 Changed - **scope**: description ### 🐛 Fixed - description ### 🔥 Removed - description ### ⚙️ Technical - description ``` ## Output Rules - **Rewrite descriptions** — do not copy commit subjects verbatim. Rephrase into clear, human-readable sentences. Use backticks for code references (skill names, commands, files, config keys). Capitalize the first word. - **Omit empty categories** — only show categories that have commits - **Scope as bold prefix** when present: `- **scope**: description` - **No scope**: just `- description` - **Skip merge commits** — ignore subjects starting with `Merge` - **Include task numbers** when present: `- **scope**: description (TASK-123)` - **English only** ## Edge Cases - **No tag found**: use all commits and suggest `v0.1.0` - **No commits since tag**: output "No changes since `<tag>`." - **Unrecognized format**: classify under "Other" with the full subject as description - **Multiple breaking changes**: still one major bump, list all in a `### ⚠️ Breaking Changes` section at the top ## Example **Input commits** (from `git log v1.2.0..HEAD`): ``` ✨ feat(auth): add OAuth2 login with Google (NTT-128) 🐛 fix(exports): prevent duplicate rows in CSV export 🔨 patch(ui): improve loading spinner animation ♻️ refactor: simplify database connection pooling 🔥 remove(api): drop deprecated v1 endpoints ``` **Output**: ```markdown ## v1.3.0 - 2026-02-12 ### ✨ Added - **auth**: `OAuth2` login with Google provider (NTT-128) ### 🔨 Changed - **ui**: Improve the loading spinner animation ### 🐛 Fixed - **exports**: Fix duplicate rows appearing in CSV exports ### 🔥 Removed - **api**: Drop deprecated `v1` API endpoints ### ⚙️ Technical - Simplify database connection pooling ``` Suggested version: **v1.3.0** (minor bump — contains new feature)
Related Skills
bgo
Automates the complete Blender build-go workflow, from building and packaging your extension/add-on to removing old versions, installing, enabling, and launching Blender for quick testing and iteration.
google-docs-manager
Expert in Google Docs management. Use when creating, reading, updating, formatting, or managing Google Docs with markdown support, advanced formatting, tables with full manipulation, images with styling, lists, headers/footers, and table of contents.
genesis-tools:living-docs
Self-maintaining documentation system. Bootstraps, validates, refines, and optimizes codebase documentation. Creates minimal, token-efficient doc chunks. Use when creating, updating, or auditing project documentation.
generate-docstrings
Create docstrings for functions and classes. Use when documenting code APIs.
generate-agent-docs
Generates documentation and usage guides for agents, skills, prompts, and instructions. Works with GitHub Copilot, Claude Code, Codex, OpenCode, and other providers. Use when onboarding team members, creating README files for your customizations, or generating usage examples for existing agents.
flow-documenter
Document findings and maintain task notes using Flow framework. Use when user says "document", "document this", "document finding", "add notes", "add this to notes", "write this down", "summarize", "summarize this", "generate changelog", "create changelog", or wants to capture discoveries. Helps update task Notes sections, create summaries with /flow-summarize, and keep documentation synchronized with work. Focuses on concise, actionable documentation.
fix-markdown
Fix lint, formatting, and prose issues in markdown files using Prettier and Vale. Use when the user or agent needs to fix lint, formatting, and prose issues in markdown files.
file-placement
Activate when creating any summary, report, or output file. Ensures files go to correct directories (summaries/, memory/, stories/, bugs/). Mirrors what summary-file-enforcement hook enforces.
feature-docs
[Documentation] Create or update business feature documentation in docs/business-features/{Module}/. Generates comprehensive 26-section docs with verified code evidence and AI companion files. Triggers on: feature docs, business feature documentation, module documentation, document feature, update feature docs, ai companion, ai context file, quick feature docs, feature readme, single file docs, verified documentation.
faf-docs
Access FAF documentation, guides, and resources. Answers questions about The Reading Order, IANA registration, Podium scoring, format specification, and best practices. Use when user asks "how does FAF work", "show me docs", "explain The Reading Order", or needs reference information.
explanation-docs
Explanation documentation patterns for understanding-oriented content - conceptual guides that explain why things work the way they do
executing-plans
Execute implementation plans with batch processing and review checkpoints. Use when given a plan document.