How do I install the Changelog skill?

Run npx skillmds@latest add tomevault-io/changelog-8 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.

Is Changelog safe to use?

This skill has not completed SkillMD's automated safety review yet. Independent scanners report: SkillSpector: PASS, Skill Scanner: PASS. 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?

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

Changelog by tomevault-io — Agent Skill

Name: Changelog
Author: tomevault-io

Changelog

Manages CHANGELOG.md entries following Keep a Changelog format. Use when adding changelog entries, documenting changes, updating release notes, or preparing for a release. Triggers on terms like "changelog", "document changes", "release notes", "what changed".

tomevault-io Updated Sep 17, 2026

File contents

Changelog Management Skill

This skill helps maintain CHANGELOG.md following Keep a Changelog format.

Changelog Structure

# 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).

## [Unreleased]

## [X.Y.Z] - YYYY-MM-DD

### Added
### Changed
### Deprecated
### Removed
### Fixed
### Security

[Unreleased]: https://github.com/rust-works/omni-dev/compare/vX.Y.Z...HEAD
[X.Y.Z]: https://github.com/rust-works/omni-dev/compare/vX.Y.Z-1...vX.Y.Z

Category	Use For
Added	New features
Changed	Changes in existing functionality
Deprecated	Soon-to-be removed features
Removed	Now removed features
Fixed	Bug fixes
Security	Vulnerability fixes
Documentation	Documentation-only changes
Refactored	Code changes that don't affect behavior

Entry Format

Each entry should:

Start with **Bold Feature Name**: followed by description
Use sub-bullets for implementation details
Be written in past tense for releases, present for unreleased

Good Example

### Added
- **Commit Message Validation Command**: New `check` command for validating commit messages
  - AI-powered analysis with configurable severity levels
  - Multiple output formats (text, JSON, YAML) for CI/CD integration
  - Smart exit codes for pipeline integration

Bad Example

### Added
- Added check command
- It validates commits

Key Learnings

Incremental Updates

Add entries to [Unreleased] as features are merged, not all at once during release. This:

Makes release prep faster
Ensures nothing is missed
Provides better commit-to-changelog traceability

Version Links

Always maintain comparison links at the bottom of the file:

[Unreleased]: https://github.com/rust-works/omni-dev/compare/vX.Y.Z...HEAD
[X.Y.Z]: https://github.com/rust-works/omni-dev/compare/vX.Y.Z-1...vX.Y.Z

When releasing:

Update [Unreleased] link to compare against new version
Add new version's comparison link

Gathering Changes

To see what changed since last release:

# Get last release tag
git describe --tags --abbrev=0

# Show commits since last release
git log --oneline $(git describe --tags --abbrev=0)..HEAD

# Show detailed commit info
git show <commit-hash> --stat

Instructions

Read current CHANGELOG.md
Identify the appropriate category for changes
Write clear, descriptive entries with details
For releases, move [Unreleased] content to new version section
Update version comparison links

Converted and distributed by TomeVault — claim your Tome and manage your conversions.

---name: changelog-8description: Manages CHANGELOG.md entries following Keep a Changelog format. Use when adding changelog entries, documenting changes, updating release notes, or preparing for a release. Triggers on terms like "changelog", "document changes", "release notes", "what changed".---# Changelog Management SkillThis skill helps maintain CHANGELOG.md following [Keep a Changelog](https://keepachangelog.com/) format.## Changelog Structure```markdown# ChangelogAll 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).## [Unreleased]## [X.Y.Z] - YYYY-MM-DD### Added### Changed### Deprecated### Removed### Fixed### Security[Unreleased]: https://github.com/rust-works/omni-dev/compare/vX.Y.Z...HEAD[X.Y.Z]: https://github.com/rust-works/omni-dev/compare/vX.Y.Z-1...vX.Y.Z```## Categories| Category | Use For ||-------------------|-----------------------------------------|| **Added** | New features || **Changed** | Changes in existing functionality || **Deprecated** | Soon-to-be removed features || **Removed** | Now removed features || **Fixed** | Bug fixes || **Security** | Vulnerability fixes || **Documentation** | Documentation-only changes || **Refactored** | Code changes that don't affect behavior |## Entry FormatEach entry should:- Start with `**Bold Feature Name**:` followed by description- Use sub-bullets for implementation details- Be written in past tense for releases, present for unreleased### Good Example```markdown### Added- **Commit Message Validation Command**: New `check` command for validating commit messages - AI-powered analysis with configurable severity levels - Multiple output formats (text, JSON, YAML) for CI/CD integration - Smart exit codes for pipeline integration```### Bad Example```markdown### Added- Added check command- It validates commits```## Key Learnings### Incremental UpdatesAdd entries to `[Unreleased]` as features are merged, not all at once during release. This:- Makes release prep faster- Ensures nothing is missed- Provides better commit-to-changelog traceability### Version LinksAlways maintain comparison links at the bottom of the file:```markdown[Unreleased]: https://github.com/rust-works/omni-dev/compare/vX.Y.Z...HEAD[X.Y.Z]: https://github.com/rust-works/omni-dev/compare/vX.Y.Z-1...vX.Y.Z```When releasing:1. Update `[Unreleased]` link to compare against new version2. Add new version's comparison link### Gathering ChangesTo see what changed since last release:```bash# Get last release taggit describe --tags --abbrev=0# Show commits since last releasegit log --oneline $(git describe --tags --abbrev=0)..HEAD# Show detailed commit infogit show <commit-hash> --stat```## Instructions1. Read current CHANGELOG.md2. Identify the appropriate category for changes3. Write clear, descriptive entries with details4. For releases, move `[Unreleased]` content to new version section5. Update version comparison links---> Converted and distributed by [TomeVault](https://tomevault.io/claim/rust-works) — claim your Tome and manage your conversions.

Frequently asked questions