skills.rest
enoch-robinson
enoch-robinsonCOMMUNITY
Explore all skills by this author →
GitHub

changelog-writer

Generate standardized Keep a Changelog entries from commits or release notes.

Updated Jan 10, 2026
Search Tags:#automation#changelog#documentation#semver#release-notes#commit-messages#keep-a-changelog
One-click install
npx skills add https://github.com/enoch-robinson/agent-skill-collection --skill changelog-writer-enoch-robinson
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: changelog-writer
Source: https://github.com/enoch-robinson/agent-skill-collection/tree/main/skills/documents/changelog-writer
Command: npx skills add https://github.com/enoch-robinson/agent-skill-collection --skill changelog-writer-enoch-robinson

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Changelog management is tedious; teams struggle to produce clear, standardized release notes that communicate changes to users and stakeholders.

Core Features & Use Cases

  • Keep a Changelog compliant: Generate well-structured entries following keep-a-changelog format.
  • SemVer-ready: Outline changes by major, minor, and patch levels, enabling accurate versioning.
  • Automated draft creation: Convert commit messages or release items into ready-to-publish entries.
  • Use Case: A developer team wants to publish a release with sections for Added, Changed, Fixed, and Security; this skill produces that structure.

Quick Start

Provide a list of changes (commits, issues, or notes) and specify the target version; the skill will output a complete changelog section ready for your release notes.

Frequently Asked Questions about changelog-writer

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

FAQPage Schema
How do I generate release notes from commit messages?▼

Generate release notes by providing a list of commit messages, issues, or plain text changes along with a target version to produce a complete, ready-to-publish Keep a Changelog entry.

What is the Keep a Changelog format for software documentation?▼

The Keep a Changelog format structures software documentation into standardized sections like Added, Changed, Deprecated, Removed, Fixed, and Security to clearly communicate changes to users and stakeholders.

Can I use semantic versioning sections for my changelog?▼

Yes, semantic versioning is supported to outline changes by major, minor, and patch levels, ensuring accurate versioning and structured categorization within your release notes.

Do I need external tooling to create a standardized changelog?▼

No external tooling is required to create a standardized changelog; you only need to provide plain text input containing your release items, commit messages, or issue data.

What is the best way to automate changelog draft creation?▼

Automate changelog draft creation by inputting raw release items into a generator that applies Keep a Changelog structure and semantic versioning rules to output publish-ready documentation.

Related Skills

Explore More Content & Communication Skills→
Camilo8902Camilo8902

conventional-commits

Generate semantic commit messages following the Conventional Commits specification.

Community
Intermediate
li3pli3p

changelog

Generate human-readable changelog entries from git history and diffs.

Community
Advanced
DrLuggelsDrLuggels
3

changelog-automation

Generate changelogs and release notes from Conventional Commits.

Community
Advanced
xloxn69xloxn69
7

changelog-entry

Generate Keep a Changelog format release notes with version headers and categories.

Community
Basic