Auto Git Changelog

The problem

Manually tracking every git commit to build a release note is tedious and prone to human error. Developers often lose track of which changes belong to which category, leading to disorganized or missing changelog entries.

What it does

• Executes git log commands to retrieve recent commit history automatically.
• Groups raw commit messages into standard categories like Added, Changed, Fixed, and Security.
• Formats output following the industry-standard Keep a Changelog specification.
• Auto-detects and prepends new entries to existing CHANGELOG.md files or creates them from scratch.

Frameworks & tools

Git, Markdown, Shell.

Why this beats prompting it yourself

Standard LLM prompts often hallucinate commit dates or miss specific changes because they lack direct repository access. This skill integrates directly with your local git history to ensure every entry is based on actual repository state, not just memory.

Use cases

• Generating release notes for a new software version tag.
• Updating a CHANGELOG.md file before a pull request merge.
• Summarizing the last 20 commits for a team standup or status report.
• Scaffolding a new changelog file for a legacy project.

Known limitations

Requires git to be installed and initialized in the target directory. It cannot pull commits from remote repositories without local clones.