Git Changelog

What This Skill Does

The Git Changelog skill for OpenClaw is a powerful utility designed to bridge the gap between technical git history and human-readable documentation. It automates the tedious process of auditing git commits, parsing them against the Conventional Commits specification, and structuring them into a professional-grade Markdown changelog. By identifying version ranges, extracting metadata, and categorizing changes (such as features, bug fixes, and breaking changes), it ensures your project documentation stays perfectly in sync with your codebase evolution. It also intelligently handles repository metadata to generate clickable commit links, making navigation easier for your end users.

Installation

To integrate this skill into your OpenClaw environment, execute the following command in your terminal: clawhub install openclaw/skills/skills/sa9saq/git-changelog

Use Cases

• Automated Release Notes: Generate professional documentation for GitHub releases automatically whenever a new tag is pushed.
• Project Auditing: Summarize all changes between two specific points in history to prepare for a stakeholder audit or team retrospective.
• Documentation Maintenance: Automatically update a root CHANGELOG.md file to maintain a clean project history without manual editing.
• Version Tracking: Quickly identify which features or fixes were introduced since the last deployment, ensuring better visibility during the release cycle.

Example Prompts

1. "Generate a changelog for all commits since the last tag and append it to my CHANGELOG.md file."
2. "Show me a summary of all 'fix' and 'feat' commits from the last month in the current repository."
3. "Create release notes for version 2.0.0 based on the commit history since the v1.9.0 tag, and format it with links to the GitHub commits."

Tips & Limitations

• Conventional Commits: For the best results, ensure your team follows the conventional commit standard (e.g., feat:, fix:, chore:). If your history does not follow this format, the skill gracefully falls back to a chronological summary.
• Performance: For extremely large repositories with thousands of commits, focus your range using the --since or --until flags to optimize execution speed.
• Permissions: This skill requires read access to your local git repository. If you choose to use the automatic write feature, ensure the skill has file-write permissions enabled for the directory.