Slash Command

/changelog

Parses git history since last release tag, categorizes commits by type, generates Keep a Changelog markdown with next version suggestion, and offers to prepend to CHANGELOG.md.

Git

documentation

npx claudepluginhub rohitg00/awesome-claude-code-toolkit --plugin smart-commit

Popularity

Parent stars

1,716

Parent forks

535

Invocation

How this command is triggered — by the user, by Claude, or both

Slash command

/smart-commit:changelog

Model invocable

No pre-commands

Context Preview

The summary Claude sees in its command listing — used to decide when to auto-load this command

# /smart-commit:changelog

Parse the git history since the last release tag and generate a structured markdown changelog.

## Process

1. Identify the latest release tag by running `git tag --sort=-v:refname | head -20`.
   - Look for semver-formatted tags (v1.2.3, 1.2.3, etc.)
   - If no tags exist, use the initial commit as the starting point

2. Retrieve all commits since the last tag:
   

3. Parse each commit message and categorize by conventional commit type:
   - **Added** - `feat` commits introducing new functionality
   - **Fixed** - `fix` commits correcting bugs or errors
   - **C...

Command Content

65 lines · ~575 tokens

Other plugins with /changelog

/changelog

1.7k

Generates changelog from git history since last tag or reference, grouping conventional commits by type (Features, Fixes, etc.), highlighting breaking changes, in Keep a Changelog format with version bump suggestion.

claude-code-toolkit

/changelog

Generates a Keep a Changelog from git commits since last release tag or specified starting point (tag, version, commit ref, or date), parsing Conventional Commits into sections like Added, Fixed, Changed.

4 tools

productivity

/generate-changelog

1.7k

Generates changelog from git history using conventional commits, grouping by type and version. Updates or prepends to CHANGELOG.md in Keep a Changelog format. Supports --from and --to flags.

changelog-gen

/changelog

Generates changelogs from git commit history with automatic categorization, semantic versioning detection, and multiple output formats.

git

/changelog

2.3k

Generate structured changelog from recent git commits, grouped by date and categorized by type (features, fixes, etc.) in markdown format.

deep-wiki

/write-changelog

1.7k

Generates detailed changelog entry from git commits and merged PRs since last release tag. Classifies changes, adds user-facing descriptions with PR links and credits, prepends to CHANGELOG.md.

changelog-writer

Stats

LanguageJavaScript

Parent stars1,716

Parent forks535

MaintenanceFair

Last CommitFeb 4, 2026

Actions

View Source View Plugin View on GitHub View README

Help us improve

Share bugs, ideas, or general feedback.

Stats

Actions

Help us improve

Share bugs, ideas, or general feedback.

# /smart-commit:changelog Parse the git history since the last release tag and generate a structured markdown changelog. ## Process 1. Identify the latest release tag by running `git tag --sort=-v:refname | head -20`. - Look for semver-formatted tags (v1.2.3, 1.2.3, etc.) - If no tags exist, use the initial commit as the starting point 2. Retrieve all commits since the last tag: 3. Parse each commit message and categorize by conventional commit type: - **Added** - `feat` commits introducing new functionality - **Fixed** - `fix` commits correcting bugs or errors - **C...

/smart-commit:changelog

Parse the git history since the last release tag and generate a structured markdown changelog.

Process

Identify the latest release tag by running git tag --sort=-v:refname | head -20.

Look for semver-formatted tags (v1.2.3, 1.2.3, etc.)
If no tags exist, use the initial commit as the starting point

Retrieve all commits since the last tag:

git log <last-tag>..HEAD --pretty=format:"%H|%s|%an|%ad" --date=short

Parse each commit message and categorize by conventional commit type:

Added - feat commits introducing new functionality
Fixed - fix commits correcting bugs or errors
Changed - refactor, perf, style commits modifying existing behavior
Deprecated - commits mentioning deprecation in subject or body
Removed - commits removing features, files, or dead code
Security - commits addressing vulnerabilities or security concerns
Documentation - docs commits
Internal - chore, ci, test, build commits

For each commit entry, format as:

Concise description derived from the commit subject
Scope in parentheses if present
Shortened commit hash as a reference

Suggest the next version number based on changes:

MAJOR bump if any BREAKING CHANGE footers are present
MINOR bump if any feat commits are present
PATCH bump if only fix, refactor, perf, docs, chore commits

Generate the changelog in Keep a Changelog format.

Output Format

## [X.Y.Z] - YYYY-MM-DD ### Added - Description of new feature (scope) [`abc1234`] ### Fixed - Description of bug fix (scope) [`def5678`] ### Changed - Description of modification (scope) [`ghi9012`] ### Internal - Description of internal change [`jkl3456`]

Rules

Group entries by category, not chronologically

Omit empty categories entirely

Keep descriptions user-facing: translate technical commits into impact statements

If a commit message is unclear, read the diff with git show <hash> --stat for context

Merge commits and revert-of-reverts should be excluded

Present the changelog for review before writing to CHANGELOG.md

Prepend to existing CHANGELOG.md if one exists, do not overwrite history

/smart-commit:changelog

Parse the git history since the last release tag and generate a structured markdown changelog.

Process

Identify the latest release tag by running git tag --sort=-v:refname | head -20.

Look for semver-formatted tags (v1.2.3, 1.2.3, etc.)
If no tags exist, use the initial commit as the starting point

Retrieve all commits since the last tag:

git log <last-tag>..HEAD --pretty=format:"%H|%s|%an|%ad" --date=short

Parse each commit message and categorize by conventional commit type:

Added - feat commits introducing new functionality
Fixed - fix commits correcting bugs or errors
Changed - refactor, perf, style commits modifying existing behavior
Deprecated - commits mentioning deprecation in subject or body
Removed - commits removing features, files, or dead code
Security - commits addressing vulnerabilities or security concerns
Documentation - docs commits
Internal - chore, ci, test, build commits

For each commit entry, format as:

Concise description derived from the commit subject
Scope in parentheses if present
Shortened commit hash as a reference

Suggest the next version number based on changes:

MAJOR bump if any BREAKING CHANGE footers are present
MINOR bump if any feat commits are present
PATCH bump if only fix, refactor, perf, docs, chore commits

Generate the changelog in Keep a Changelog format.

Output Format

Rules

Group entries by category, not chronologically

Omit empty categories entirely

Keep descriptions user-facing: translate technical commits into impact statements

If a commit message is unclear, read the diff with git show <hash> --stat for context

Merge commits and revert-of-reverts should be excluded

Present the changelog for review before writing to CHANGELOG.md

Prepend to existing CHANGELOG.md if one exists, do not overwrite history

/changelog

Popularity

Invocation

Context Preview

Command Content

Other plugins with /changelog

Help us improve

Help us improve

Find plugins for your project

/changelog

Popularity

Invocation

Context Preview

Command Content

/smart-commit:changelog

Process

Output Format

Rules

Other plugins with /changelog

Help us improve

/smart-commit:changelog

Process

Output Format

Rules