git-changelog

What This Skill Does

The git-changelog skill acts as an automated release assistant for developers, parsing git history into professional, human-readable changelogs. By adhering to Conventional Commits standards, it intelligently extracts commit metadata—such as types (feat, fix, refactor), scopes, and breaking changes—to produce a structured Markdown document. It features smart range detection, allowing you to generate reports since your last tag, within a specific date range, or for the entire project history. The output is formatted with appropriate emojis and clear hierarchies, making it ready for GitHub releases or project documentation files.

Installation

You can install this skill directly via the OpenClaw CLI: clawhub install openclaw/skills/skills/fratua/git-changelog

Use Cases

• Project Maintenance: Quickly summarize changes before merging a feature branch into main.
• Release Management: Automatically draft the body of a GitHub release based on tags.
• Team Communication: Generate periodic project summaries for stakeholders without manually digging through commit logs.
• Repository Cleanup: Maintain a high-quality CHANGELOG.md file that strictly follows semver and release history.

Example Prompts

1. "Generate a changelog for all changes since the last tag and output it to my CHANGELOG.md file."
2. "Show me a list of all features and bug fixes added to this project between January 1st and February 1st, 2025."
3. "Summarize the last 50 commits into a markdown report formatted for our release notes."

Tips & Limitations

• Conventional Commits: This skill works best when the repository strictly follows the type(scope): description format. If your commit history is inconsistent, some commits may fall into the 'Other' category.
• Range Flexibility: If you haven't used tags in your project, the skill defaults to the full history; ensure your initial history is clean to avoid overly verbose output.
• Breaking Changes: Always review the 'Breaking Changes' section generated at the top; the skill detects these via the ! convention or the BREAKING CHANGE body footer, but human verification is recommended for major version transitions.
• Write Access: Be aware that requesting the skill to update CHANGELOG.md will modify your local filesystem. Always commit or stash your work before running automated file updates.