changelog

Generate release notes and changelogs from git history and pull requests.

Updated Feb 17, 2026
One-click install
npx skills add https://github.com/aakash-dhar/claude-skills --skill changelog-aakash-dhar
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: changelog
Source: https://github.com/aakash-dhar/claude-skills/tree/main/skills/changelog
Command: npx skills add https://github.com/aakash-dhar/claude-skills --skill changelog-aakash-dhar

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) and references (resource) components.

What problem does it solve?

This Skill automates the creation of release notes and changelogs by analyzing your project's git history, commits, and pull requests, ensuring clear and consistent communication of changes.

Core Features & Use Cases

  • Automated Change Analysis: Gathers commits, PRs, and tags to identify what has changed.
  • Categorization: Parses conventional commits or analyzes diffs to categorize changes (features, fixes, breaking changes, etc.).
  • Multiple Formats: Generates changelogs in various formats suitable for libraries, products, or internal teams.
  • Version Bumping: Suggests appropriate semantic version bumps (MAJOR, MINOR, PATCH).
  • Platform Integration: Provides commands for creating Git tags, GitHub/GitLab releases, and publishing packages.

Quick Start

Use the changelog skill to generate release notes for the next version based on your git history.

Frequently Asked Questions about changelog

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I generate release notes from git history automatically?

To generate release notes from git history automatically, this Skill analyzes your project's commits, pull requests, and tags. It parses conventional commits and analyzes diffs to categorize changes into features, fixes, and breaking changes for your release notes.

Does this tool support conventional commit parsing for changelog categorization?

Yes, conventional commit parsing is fully supported for changelog categorization. The tool reads your conventional commits to automatically categorize changes into features, fixes, and breaking changes, ensuring clear and consistent release notes.

Can I create GitHub or GitLab releases directly from generated changelogs?

You can create GitHub or GitLab releases directly from generated changelogs using built-in platform integration commands. It also supports creating Git tags and publishing packages to streamline your versioning and release workflow.

What is the best way to determine semantic version bumps from git commits?

The best way to determine semantic version bumps from git commits is by analyzing commit history for breaking changes, features, and fixes. The Skill suggests appropriate MAJOR, MINOR, or PATCH version bumps based on your parsed git history.

What changelog formats are available for developer and user-facing release notes?

Available changelog formats include Keep a Changelog, developer-facing, and user-facing formats. These multiple output formats ensure the release notes are suitable for libraries, products, or internal teams based on your specific needs.