Changelog Writer Skill

What this skill does

Commit messages are written for other developers, but changelogs are read by users — and translating between the two by hand at release time is a tedious, easy-to-skip step. This skill takes a batch of commit messages or merged PR titles/descriptions and writes a clean, user-facing changelog entry organized by category.

How it works

1. Change classification — reads each commit/PR and classifies it as a feature, fix, improvement, or internal-only change (internal changes are dropped from the user-facing output by default).
2. Entry drafting — rewrites the surviving items in plain, user-facing language (no ticket numbers, no internal jargon) and groups them under Added, Fixed, and Improved headings.
3. Version header — adds a version/date header matching your project's existing changelog format, if one is supplied as a style reference.

Requirements

• Works on Claude AI (Claude Code, reading from local git log) and on OpenClaw (reading from a GitHub/GitLab API pull of merged PRs).
• No external API required beyond your existing git repository or already-configured Git plugin access.

Setup

1. Unzip the package into your Skills directory, keeping the folder structure intact.
2. (Optional) Provide a sample of your existing changelog format in examples/style-reference.md so new entries match your house style.
3. Invoke it with a commit range (git log v1.2.0..HEAD) or a list of merged PRs — see SKILL.md for the exact input formats.

What's included

• SKILL.md — the skill definition and classification/drafting logic
• examples/style-reference.md — placeholder for your changelog's existing format
• examples/sample-run.md — a worked example from a sample commit range