How do I install the Changelog skill?

Run npx skillmds add majiayu000/changelog-4 in your terminal (requires Node.js), paste this page's agent-chat prompt into Claude, Cursor, or any MCP-connected agent, or download the SKILL.md file and copy it into your agent's skills directory.

What does the Changelog skill do?

Generate a Keep a Changelog entry from git commits It is listed under Coding & Dev Tools on SkillMD.

Is Changelog safe to use?

This skill has not completed SkillMD's automated safety review yet. Capability flags: makes network calls, reads secrets. SkillMD never runs a skill's scripts for you; review the SKILL.md before installing.

Which AI agents work with Changelog?

This skill is tagged as working with Claude Code, Claude.ai, OpenAI Codex. SKILL.md is an open format, so most agents that read a skills directory can load it too.

Is Changelog free to use?

Yes. Installing skills from SkillMD is free, and the skill stays under its author's original license.

Who published Changelog?

majiayu000 (@majiayu000) published this skill. Their other Agent Skills are listed on their SkillMD profile.

Changelog by majiayu000 — Agent Skill

Name: Changelog
Rating: 4.2 (5 reviews)
Author: majiayu000

File contents

/changelog - Generate Changelog Entry

Purpose

Generate a Keep a Changelog entry matching the existing CHANGELOG.md style, if available.

Usage

/changelog [version]

Version is optional — suggest one based on the changes (patch for fixes, minor for features, major for breaking changes).

Process

Find the last tag and get commits

git describe --tags --abbrev=0
git log --pretty=format:'%s' <tag>..HEAD

Categorize using Keep a Changelog sections
- ### Features — new capabilities
- ### Changed — breaking or notable behavior changes
- ### Enhancements — improvements to existing features
- ### Bug Fixes — things that were broken
- ### Removed — removed features (rare)
Write entries in a consistent voice

Match the existing style:
- Start with imperative verb or noun phrase
- Bold key concepts on first mention: **Overlay commit model for file writes**:
- Sub-bullets for details when a feature has multiple parts
- Technical but accessible — users are developers
Examples:
- Fix login regression: use OAuth2 instead of deprecated token flow
- Improve CLI help with quick start guide and clearer description
- **Remote file sync**: sync_remote() now supports conflict detection
Skip internal-only changes

Omit: CI tweaks, refactoring without user impact, dependency bumps (unless security-related)

Output format

## [x.y.z] - YYYY-MM-DD

### Features

- **Feature name**: Description of what users can now do

### Bug Fixes

- Fix specific thing that was broken

Prepend to CHANGELOG.md

If CHANGELOG.md doesn't exist, create it with this header:

# Changelog

All notable changes to this project will be documented in this file.

The format is based on [Keep a Changelog](https://keepachangelog.com/en/1.0.0/),
and this project adheres to [Semantic Versioning](https://semver.org/spec/v2.0.0.html).

If an ## [Unreleased] section exists, insert after it. Otherwise, insert after the file header (title and any preamble), before the first version entry.

Notes

Keep sections in order: Features → Changed → Enhancements → Bug Fixes → Removed
Omit empty sections
Date format: YYYY-MM-DD
If unsure about version bump, ask

---name: changelog-4description: Generate a Keep a Changelog entry from git commits--- # /changelog - Generate Changelog Entry ## Purpose Generate a Keep a Changelog entry matching the existing CHANGELOG.md style, if available. ## Usage ``` /changelog [version] ``` Version is optional — suggest one based on the changes (patch for fixes, minor for features, major for breaking changes). ## Process 1. **Find the last tag and get commits** ``` git describe --tags --abbrev=0 git log --pretty=format:'%s' <tag>..HEAD ``` 2. **Categorize using Keep a Changelog sections** - `### Features` — new capabilities - `### Changed` — breaking or notable behavior changes - `### Enhancements` — improvements to existing features - `### Bug Fixes` — things that were broken - `### Removed` — removed features (rare) 3. **Write entries in a consistent voice** Match the existing style: - Start with imperative verb or noun phrase - Bold key concepts on first mention: `**Overlay commit model for file writes**:` - Sub-bullets for details when a feature has multiple parts - Technical but accessible — users are developers Examples: - `Fix login regression: use OAuth2 instead of deprecated token flow` - `Improve CLI help with quick start guide and clearer description` - `**Remote file sync**: sync_remote() now supports conflict detection` 4. **Skip internal-only changes** Omit: CI tweaks, refactoring without user impact, dependency bumps (unless security-related) 5. **Output format** ```markdown ## [x.y.z] - YYYY-MM-DD ### Features - **Feature name**: Description of what users can now do ### Bug Fixes - Fix specific thing that was broken ``` 6. **Prepend to CHANGELOG.md** If CHANGELOG.md doesn't exist, create it with this header: ```markdown # Changelog All notable changes to this project will be documented in this file. The format is based on [Keep a Changelog](https://keepachangelog.com/en/1.0.0/), and this project adheres to [Semantic Versioning](https://semver.org/spec/v2.0.0.html). ``` If an `## [Unreleased]` section exists, insert after it. Otherwise, insert after the file header (title and any preamble), before the first version entry. ## Notes - Keep sections in order: Features → Changed → Enhancements → Bug Fixes → Removed - Omit empty sections - Date format: YYYY-MM-DD - If unsure about version bump, ask

Frequently asked questions