changelog

Name: changelog
Availability: InStock
Author: pixl

Generate grouped markdown changelog entries from conventional commit histories.

2|Updated Mar 16, 2026

Search Tags:#automation #git #changelog #versioning #ci #release-notes #conventional-commits

Ready to run

npx skills add https://github.com/hamzaPixl/pixl-ai --skill changelog-hamzapixl

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: changelog
Source: https://github.com/hamzaPixl/pixl-ai/tree/main/packages/crew/skills/changelog
Command: npx skills add https://github.com/hamzaPixl/pixl-ai --skill changelog-hamzapixl

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Automates the creation of release notes by parsing conventional commits and assembling a structured markdown changelog, eliminating manual aggregation and reducing release-day friction.

Core Features & Use Cases

Conventional Commit Parsing: Extracts commit type, optional scope, description, and breaking change indicators from commit messages.
Grouped Markdown Output: Produces a version- and date-stamped changelog entry grouped into Features, Bug Fixes, Refactoring, Breaking Changes, and Other, omitting empty sections and using short commit hashes.
Dry-run and File Output: Supports previewing the changelog entry or prepending it to CHANGELOG.md or a specified output path; attempts to read version from pyproject.toml or package.json when available.
Use Case: Prepare release notes for a new release by converting commits since the last tag into a clear, repeatable markdown entry for CHANGELOG.md or release descriptions.

Quick Start

Generate a markdown changelog for commits since the last git tag and print it as a dry-run preview.

Frequently Asked Questions about changelog

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

FAQPage Schema

How do I auto-generate a changelog from conventional commits?▼

You can generate release notes from conventional commits by parsing git log output and grouping entries by commit type into a version-stamped markdown changelog. It automatically categorizes features, fixes, refactors, and breaking changes.

What is the best way to group git commit messages into release notes?▼

Grouping git commit messages into release notes is best handled by parsing conventional commit histories and categorizing them into Features, Bug Fixes, Refactoring, and Breaking Changes. This process omits empty sections and includes short commit hashes for traceability.

Can I preview changelog markdown before writing to a file?▼

Yes, you can preview changelog markdown before writing to a file using the dry-run preview option. This allows you to inspect the generated release notes entry before prepending it to your CHANGELOG.md or specified output path.

Does the changelog generator detect project versions from package files?▼

The changelog generator detects project versions by reading from pyproject.toml or package.json when available. It also detects git tags to determine the commit range and stamps the generated markdown entry with the extracted version and date.

How do I prepend release notes to an existing CHANGELOG.md file?▼

To prepend release notes to an existing CHANGELOG.md, the Skill generates a markdown entry from your commits since the last tag and writes it directly to the top of the specified output file. This maintains chronological order for your release history.

Do I need conventional commit messages to generate grouped markdown release notes?▼

Yes, you need conventional commit messages to generate grouped markdown release notes. The parser relies on conventional commit formatting to extract the commit type, optional scope, description, and breaking change indicators required for accurate categorization.