skills.rest
yangqiong
yangqiongCOMMUNITY
Explore all skills by this author →
GitHub

Changelog Skill

Generate and maintain project changelogs following Keep a Changelog and Semantic Versioning.

Updated Dec 24, 2025
Search Tags:#changelog#best practices#versioning#documentation#release notes
One-click install
npx skills add https://github.com/yangqiong/claude-skills --skill changelog-skill
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: Changelog Skill
Source: https://github.com/yangqiong/claude-skills/tree/main/documentation/changelog
Command: npx skills add https://github.com/yangqiong/claude-skills --skill changelog-skill

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This Skill helps you create and maintain clear, informative project changelogs that adhere to best practices, making it easier for users and contributors to understand project evolution.

Core Features & Use Cases

  • Adherence to "Keep a Changelog": Ensures changelogs are human-readable and follow established conventions.
  • Structured Entries: Organizes changes by type (Added, Changed, Fixed, etc.) and version.
  • Use Case: When preparing for a new release, use this Skill to generate a well-formatted changelog entry based on recent commits and development notes, ensuring all significant changes are documented.

Quick Start

Use the changelog skill to generate a new entry for the 'Unreleased' section.

Frequently Asked Questions about Changelog Skill

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I generate a changelog following the Keep a Changelog standard?▼

To generate a changelog following the Keep a Changelog standard, structure entries by categorizing updates into Added, Changed, Fixed, or Removed sections based on recent commits and Semantic Versioning principles.

What is the best way to document release notes for software versioning?▼

The best way to document release notes for software versioning is to maintain a structured changelog that clearly communicates project updates, new features, bug fixes, and breaking changes to users and contributors.

How do I format an unreleased changelog entry before a new release?▼

To format an unreleased changelog entry before a new release, add updates to an 'Unreleased' section at the top of the document, categorizing them by type such as Added, Changed, or Fixed until the version is published.

Does this changelog format work with Semantic Versioning principles?▼

Yes, this changelog format works with Semantic Versioning principles by ensuring breaking changes, new features, and bug fixes are clearly categorized, directly aligning with major, minor, and patch version increments.

When do I need to use a structured changelog for my project documentation?▼

You need to use a structured changelog for project documentation when preparing for a release, ensuring significant changes are recorded in a human-readable format to help contributors understand project evolution.

Related Skills

Explore More Content & Communication Skills→
mattleonard16mattleonard16

changelog-generator

Translate raw git commits into customer-friendly release notes.

Community
Advanced
opensupplyhubopensupplyhub
20

release-notes

Generate formatted release notes from git logs, PRs, and migration files.

Official
Intermediate
FortiumPartnersFortiumPartners
11

Changelog Generator Skill

Generate categorized changelogs from conventional commits in markdown, JSON, or plain text.

Official
Advanced
maxenergymaxenergy

obsidian-vault

Search, create, and organize Obsidian notes using wikilinks and index notes.

Community
Intermediate