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
- 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).
- Entry drafting — rewrites the surviving items in plain, user-facing language (no ticket numbers, no internal jargon) and groups them under
Added,Fixed, andImprovedheadings. - 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
- Unzip the package into your Skills directory, keeping the folder structure intact.
- (Optional) Provide a sample of your existing changelog format so new entries match your house style.
- Invoke it with a commit range (
git log v1.2.0..HEAD) or a list of merged PRs.
What you get
- A batch of commits or merged PRs automatically classified into feature/fix/improvement/internal, with internal noise dropped
- A clean, user-facing changelog entry grouped under Added/Fixed/Improved — no ticket numbers or internal jargon
- A version/date header that matches your project's existing changelog format
- A worked example from a sample commit range to see the output quality up front