2.6k
GitHub Stars
2
Bundled Files
2 months ago
Catalog Refreshed
4 months ago
First Indexed
Readme & install
Copy the install command, review bundled files from the catalogue, and read any extended description pulled from the listing source.
Installation
Preview and clipboard use veilstrat where the catalogue uses aiagentskills.
npx veilstrat add skill openclaw/skills --skill changelog-generator-cn- _meta.json304 B
- SKILL.md3.1 KB
Overview
This skill automatically generates user-friendly changelogs by analyzing git commit history and converting technical commits into clear release notes. It groups changes into categories like features, improvements, fixes, and breaking changes, then formats the output for publishing or internal distribution. Trigger words include "changelog", "release notes", "version update", and "更新日志".
How this skill works
The skill scans a repository's git history for a specified range (since last release, date range, or specific tags). It filters out noisy commits (tests, refactors), categorizes meaningful changes, and rewrites technical messages into customer-facing language. Finally, it formats the results into a clean changelog structure ready for saving to CHANGELOG.md, release pages, app stores, or announcements.
When to use it
- Preparing release notes for a new version
- Creating weekly or monthly product update summaries
- Writing update descriptions for app stores or marketplaces
- Generating email or social media announcements about changes
- Maintaining a public changelog or internal release documentation
Best practices
- Run the tool from the repository root to capture full commit context
- Specify date ranges or tags to constrain output to the desired scope
- Provide a CHANGELOG_STYLE.md or style guidelines for consistent voice
- Review and edit generated text to align with brand tone and legal requirements
- Exclude internal-only commits by using conventional commit tags or filters
Example use cases
- Create release notes for version 2.5.0 from commits since v2.4.0
- Generate a weekly changelog summarizing all customer-facing changes
- Produce app store update text that highlights user-visible improvements
- Compile a public changelog entry that separates features, fixes, and breaking changes
- Export formatted release notes for inclusion in email newsletters
FAQ
Yes. The skill filters out commits marked as refactor, test, or chore by default and can be configured to use your project's commit conventions.
How do I control the output format?
You can provide a style guide file (e.g., CHANGELOG_STYLE.md) or choose preset formats for markdown, plain text, or release notes compatible with GitHub.