skills.rest
zinohome
zinohomeCOMMUNITY
Explore all skills by this author →
GitHub

changelog-writer

Generate changelogs and release notes from git commits, PR titles, and issue references.

1|Updated Nov 6, 2025
Search Tags:#git#changelog#versioning#documentation#conventional commits#release notes
One-click install
npx skills add https://github.com/zinohome/CozyChat --skill changelog-writer-zinohome
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: changelog-writer
Source: https://github.com/zinohome/CozyChat/tree/main/.claude/skills/changelog-writer
Command: npx skills add https://github.com/zinohome/CozyChat --skill changelog-writer-zinohome

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) and references (resource) components.

What problem does it solve?

This Skill automates the creation of professional changelogs and release notes by analyzing git commit history, making documentation a seamless part of the development process.

Core Features & Use Cases

  • Automated Changelog Generation: Parses git commits, PR titles, and issue references to create structured changelogs.
  • Categorization: Organizes changes by impact type (breaking, features, fixes, improvements).
  • Formatting: Adheres to the Keep a Changelog standard.
  • Versioning Suggestions: Provides recommendations for semantic versioning.
  • Use Case: After merging a new set of features and fixes, use this Skill to automatically generate the CHANGELOG.md file and draft release notes for the upcoming version.

Quick Start

Use the changelog-writer skill to generate release notes for the latest version.

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 git commits automatically?▼

Generate release notes by parsing git commits, PR titles, and issue references to organize changes by impact type like breaking, features, fixes, and improvements. The changelog is formatted according to the Keep a Changelog standard.

What is the best way to document version changes using semantic versioning?▼

Document version changes by categorizing git history into structured changelogs and receiving semantic versioning suggestions based on the impact type of the changes. This ensures version tags accurately reflect whether the release includes breaking changes or minor features.

Does the changelog generation follow the Keep a Changelog standard?▼

Yes, changelog generation strictly formats the output according to the Keep a Changelog standard. It structures parsed git commits and PR titles into categorized sections for breaking changes, features, fixes, and improvements.

Can I categorize git commits by impact type for my changelog?▼

Yes, you can categorize git commits by impact type. The process analyzes commit history and PR titles to automatically organize changes into breaking changes, new features, fixes, and improvements for your changelog.

How to write a changelog from conventional commits for an upcoming release?▼

Write a changelog from conventional commits by analyzing the git history and issue references to draft structured release notes. The output provides version tagging suggestions and categorizes changes by their impact type.

Related Skills

Explore More Software Engineering Skills→
micaelmaltamicaelmalta
1

git-commits

Standardize Git commit messages using Conventional Commits rules.

Community
Basic
AndrewDrygaAndrewDryga
28

release

Create semantic version tags from changelogs and push them to Git.

Community
Advanced
CleanExpoCleanExpo
1

Changelog Generator

Generate changelogs from Conventional Commits with semantic versioning for NodeJS projects.

Community
Intermediate
HomericIntelligenceHomericIntelligence
18

generate-changelog

Generate markdown changelog entries from git commit messages.

Official
Intermediate