changelog-generator

What This Skill Does

The Changelog Generator is a specialized engineering utility designed to automate the lifecycle of software release documentation. By leveraging Conventional Commit standards, the skill parses raw git history or commit streams and transforms them into structured, human-readable changelogs. It acts as an abstraction layer between chaotic git history and professional documentation, providing logic to determine semantic versioning (SemVer) bumps while rendering output into standard formats like Keep a Changelog. It includes a robust linter to enforce commit message hygiene, ensuring that all contributors adhere to the same standards before code reaches the main branch.

Installation

To integrate the Changelog Generator into your OpenClaw environment, use the standard package manager command: clawhub install openclaw/skills/skills/alirezarezvani/changelog-generator

Use Cases

This skill is indispensable for DevOps engineers and software leads managing release cadences. Use it during Continuous Integration (CI) pipelines to automatically generate release notes upon tagging a version. It is equally effective during Pull Request checks; by integrating the provided linter, you can prevent non-compliant commits from merging into production branches. Teams working in monorepos will find the scoped filtering capabilities particularly useful for separating release notes by package or subsystem, maintaining clarity even in large-scale projects.

Example Prompts

1. "Generate a changelog for the current release based on all commits between v1.3.0 and HEAD, and format it in Markdown."
2. "Lint the last five commits in my repository to ensure they comply with Conventional Commit standards, reporting any errors in JSON format."
3. "Create a summary of breaking changes since v1.2.0 and update the CHANGELOG.md file directly with a new section for version v1.3.0."

Tips & Limitations

The tool relies heavily on the quality of commit messages; if contributors use vague titles like "fix stuff," the generator will produce equally vague changelogs. Always encourage your team to use explicit types like 'feat' or 'fix'. Note that the tool is designed to prepend data; be cautious with large-scale renames or massive history re-writes, as these can produce noisy release notes. Finally, ensure that the environment running the scripts has access to the full git history, as shallow clones may lead to incomplete parsing.