smithery.ai

create-changelog

Generate or update changelogs from git history following Keep a Changelog format. Triggers: changelog, release notes, what changed, version bump, release

First seen Apr 3, 2026

Installation

$ npx skills add https://smithery.ai

Similar popular skills

Related neighbors and high-traction skills in the same topics — useful to compare before installing.

Also in this package

Other skills from smithery.ai · top by installs.

npx skills add https://smithery.ai

Browse all from smithery.ai

More details

Agent compatibility

Declared targets from SKILL.md / docs. Unmarked agents are not listed — the skill may still install via the CLI.

Claude Code Not declared
Cursor Not declared
Codex Not declared
GitHub Copilot Not declared
Windsurf Not declared
Gemini CLI Not declared
Cline Not declared
OpenCode Not declared

Skill metadata

Parsed from SKILL.md frontmatter.

Allowed toolsBash(git describe:*), Bash(git log:*), Bash(git tag:*)

Package contents

Files included with this skill beyond the listing page.

  • skill md SKILL.md 1,765 B
  • docs SUMMARY.md 41 B

History

  1. First seen on skills.sh
  2. First recorded snapshot · 2 installs

SKILL.md

Create Changelog

Generate user-friendly changelogs from git commits following Keep a Changelog specification.

Workflow

  1. Find last release point:

``bash git describe --tags --abbrev=0 2>/dev/null `` - If no tags found: use all commits

  1. Collect commits since release:

``bash git log <last-tag>..HEAD --pretty=format:"%s" --no-merges ``

  1. Categorize each commit into Keep a Changelog sections:
Section Commit patterns
Added feat:, add:, new functionality
Changed refactor:, change:, behavior modifications
Deprecated deprecate:, sunset notices
Removed remove:, delete:, dropped features
Fixed fix:, bugfix:, corrections
Security security:, vulnerability patches
  1. Write output starting DIRECTLY with version header. NO preamble, NO [Unreleased]:

```markdown ## [1.2.0] - 2025-03-15

### Added - Support for custom templates (#42) ```

  1. Write to existing changelog file, or CHANGELOG.md if none exists. Prepend new entry below the file header.

Error Recovery

  • If git log returns empty: inform user no changes found since last release
  • If commit messages lack conventional prefixes: categorize by best guess, flag uncertain entries with <!-- review --> comment
  • If existing changelog has non-standard format: preserve it, append new section at top