changelog-writer

Generate/edit changelog entries for your repository.

3|Updated Jan 29, 2026

Search Tags:#changelog #documentation #release-notes #conventional-commits #keep-a-changelog

Ready to run

npx skills add https://github.com/peopleforrester/claude-dotfiles --skill changelog-writer-peopleforrester

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: changelog-writer
Source: https://github.com/peopleforrester/claude-dotfiles/tree/main/skills/documentation/changelog-writer
Command: npx skills add https://github.com/peopleforrester/claude-dotfiles --skill changelog-writer-peopleforrester

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Generate and maintain changelogs following Keep a Changelog and Conventional Commits standards. Use when releasing versions, documenting changes, or updating project history.

Core Features & Use Cases

Generate standard Keep a Changelog compliant sections in a CHANGELOG.md
Create, update, and format release notes aligned with Conventional Commits
Apply to software releases, release planning, and ongoing project history documentation
Use case: before releasing, generate a detailed changelog covering Added, Changed, Deprecated, Removed, Fixed, and Security sections

Quick Start

Clone or open your project, run the changelog-writer to produce or update CHANGELOG.md following Keep a Changelog and Conventional Commits, then commit the updated file as part of your release.

Frequently Asked Questions about changelog-writer

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

FAQPage Schema

How do I generate a changelog following Keep a Changelog and Conventional Commits standards?▼

You can generate a changelog from Conventional Commits by running the changelog-writer tool against your project repository. It automatically formats your commit history into a standardized CHANGELOG.md file compliant with Keep a Changelog conventions.

What sections are included in a Keep a Changelog compliant release notes file?▼

A Keep a Changelog compliant release notes file organizes project history into Added, Changed, Deprecated, Removed, Fixed, and Security sections. This standardized format ensures users can easily track modifications between software releases.

Can I update an existing CHANGELOG.md or does the tool only create new files?▼

You can both create and update an existing CHANGELOG.md. The tool maintains your changelog by applying the Keep a Changelog format to new release entries, ensuring ongoing project history documentation stays aligned with your software releases.

When should I update my project changelog during the software release cycle?▼

You should update your project changelog during release planning and before publishing new software versions. Documenting changes at these stages ensures your release notes accurately capture all modifications made since the previous release.

Does this changelog generator work without any external dependencies?▼

Yes, the changelog generator operates with zero external dependencies. It independently enforces Keep a Changelog formatting and parses Conventional Commits to produce a standardized CHANGELOG.md suitable for CI/CD automation pipelines.

What is the best way to maintain project history documentation for software releases?▼

The best way to maintain project history documentation is to enforce a Keep a Changelog format combined with Conventional Commits standards. This ensures your changelog remains structured, readable, and suitable for release automation workflows.