skills.rest
faizkhairi
faizkhairiCOMMUNITY
Explore all skills by this author →
WebsiteGitHub

changelog

Generate a categorized changelog from Git history by tag, date, or commit.

64|19|Updated Mar 25, 2026
Search Tags:#changelog#release management#version control#Git#commit analysis
One-click install
npx skills add https://github.com/faizkhairi/claude-code-blueprint --skill changelog-faizkhairi
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: changelog
Source: https://github.com/faizkhairi/claude-code-blueprint/tree/main/skills/changelog
Command: npx skills add https://github.com/faizkhairi/claude-code-blueprint --skill changelog-faizkhairi

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill requires git, python, and includes scripts (resource) components.

What problem does it solve?

This Skill automates the generation of a changelog from Git history, saving time and ensuring consistency in documentation.

Core Features & Use Cases

  • Git History Analysis: Extracts commit information from Git history.
  • Commit Categorization: Categorizes commits into features, bug fixes, documentation, performance, refactoring, and other changes.
  • Output Formatting: Formats the output into a user-friendly changelog structure.
  • Use Case: Use this Skill to generate a changelog for a project release, making it easy to track changes and communicate updates to stakeholders.

Quick Start

Generate a changelog for the last release using the 'changelog' skill with the commit hash of the last tag: 'changelog --since=last-tag-commit'.

Frequently Asked Questions about changelog

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

FAQPage Schema
How do I generate a changelog from Git history?▼

You can generate a changelog from Git history by specifying a tag, date, or commit hash. This skill parses the commit history, categorizes the changes, and formats the output into a human-readable changelog structure.

How does commit categorization work for release management?▼

Commit categorization for release management works by parsing Git history and grouping commits into features, bug fixes, documentation, performance, refactoring, and other changes. This parsing relies on Python libraries to analyze and format the output.

Do I need Python and Git installed to automate changelog generation?▼

Yes, automating changelog generation requires Git to extract version control history and Python libraries to parse and categorize the commits into a structured output.

Can I generate a changelog from a specific commit hash or tag?▼

Yes, you can generate a changelog from a specific commit hash or tag. The skill filters Git history based on your specified tag, date, or commit to produce a scoped changelog for that release point.

What is the best way to format Git commit messages into a readable changelog?▼

The best way to format Git commit messages into a readable changelog is to automate extraction and categorization. This skill groups commits into structured categories like features and bug fixes, ensuring consistent documentation for stakeholders.

What are the limitations of using Python scripts for Git commit analysis?▼

A limitation of using Python scripts for Git commit analysis is that accurate categorization depends on consistent commit message formatting. The skill parses these messages to group changes, so poorly structured entries may result in generic categorization.

Related Skills

Explore More Software Engineering Skills→
alex5141alex5141

commit-conventions

Validate Git commit messages against the Conventional Commits specification.

Community
Basic
product-on-purposeproduct-on-purpose
527

deliver-release-notes

Generate user-facing release notes from changelog data.

Official
Basic
jim60105jim60105
21

bump-version

Automate semantic version bumps, changelog generation, and Git tagging.

Community
Advanced
mvillmowmvillmow
18

generate-changelog

Generate a Markdown changelog from git commits grouped by conventional commit types.

Community
Basic