write-changelog

Generates Keep a Changelog entries from git commit messages.

Updated Mar 29, 2024
One-click install
npx skills add https://github.com/petobens/ai-harness --skill write-changelog-petobens
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: write-changelog
Source: https://github.com/petobens/ai-harness/tree/main/skills/write-changelog
Command: npx skills add https://github.com/petobens/ai-harness --skill write-changelog-petobens

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Writing release notes by hand means reading through dozens of commits and formatting them consistently. This Skill automates that by reading git history and producing a structured Keep a Changelog-style entry. ## Core Features & Use Cases - Commit Summarization: Reads commit messages from specific SHAs or all commits since the latest git tag. - Keep a Changelog Formatting: Groups changes into Added, Changed, Fixed, and Removed sections with a versioned date header. - Style Matching: Reads an existing CHANGELOG.md to infer the next version and match its established style. - Use Case: Before cutting a release, ask for a changelog entry and receive a ready-to-paste markdown section summarizing every commit since the last tag. ## Quick Start Generate a changelog entry from all commits since the last release tag in this repository.

Frequently Asked Questions about write-changelog

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

FAQPage Schema
How do I generate a changelog from git commits?

Provide a repository path or run in the current directory, and the Skill reads commit messages with git log and git show, then writes a Keep a Changelog entry. By default it summarizes all commits since the latest tag found via git describe.

How to create release notes since the last git tag?

The Skill finds the latest tag using git describe --tags --abbrev=0, lists commits with git log <tag>..HEAD, and summarizes each message into grouped sections like Added, Changed, and Fixed.

Does the changelog generator edit my CHANGELOG.md file?

No, it only reads an existing CHANGELOG.md to infer the next version number and match its formatting style. The generated entry is output as markdown for you to paste or review manually.

Can I generate a changelog from specific commit SHAs?

Yes, provide a list of commit SHAs and each message is read with git show --no-patch --format=%B. The commits are then summarized and grouped into the appropriate Keep a Changelog sections.

What format does the generated changelog entry follow?

Entries follow the Keep a Changelog 1.0.0 convention with a version header like ## [1.4.0] - 2026-01-14, grouped sections, and one concise bullet per change. Commit SHAs and author names are excluded.