Setup & Installation
Or with the ClawHub CLI, for registry-managed skill folders outside a full OpenClaw workspace:
What This Skill Does
Reads git commit history and produces a categorized, markdown-formatted changelog grouped by conventional commit types. Handles tag ranges, date ranges, and breaking change detection automatically. Output is ready to paste into CHANGELOG.md or a GitHub release.
Parsing conventional commits and grouping them by type by hand is tedious and error-prone, especially across long ranges; this skill automates the whole process in one step.
When to use it
- Generating release notes before tagging a new version
- Creating a CHANGELOG.md entry after a sprint
- Reviewing what changed between two git tags
- Catching breaking changes before publishing a package
- Summarizing recent commits for a team update
Example Workflow
Here's how your AI assistant might use this skill in practice.
User asks: generate a changelog from v1.1.0 to HEAD
- 1Verify the current directory is a git repository using git rev-parse
- 2Determine the commit range from v1.1.0 to HEAD
- 3Extract commits with hash, subject, author, and date using git log
- 4Parse each commit subject for conventional commit prefixes and group into categories
- 5Check for BREAKING CHANGE footers and feat! commits, then render the full markdown output
A markdown changelog with sections for Features, Bug Fixes, and any other detected categories, including short commit hashes and scopes