changelog

...

4|Updated Apr 28, 2026

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

Ready to run

npx skills add https://github.com/vikisingh23/neuraforge-ai --skill changelog-vikisingh23

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: changelog
Source: https://github.com/vikisingh23/neuraforge-ai/tree/main/skills/changelog
Command: npx skills add https://github.com/vikisingh23/neuraforge-ai --skill changelog-vikisingh23

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This skill helps teams automatically generate a changelog from git commits, ensuring release notes are consistent and up-to-date without manual editing.

Core Features & Use Cases

Automatic changelog generation from commit history
Groups entries by type (feat, fix, docs, refactor, tests) and includes PR links for each entry
Works with conventional commits to standardize messaging and supports generating release notes

Quick Start

Run in your repository to generate a changelog from the commits since the last tag.

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 git commits?▼

Yes, you can auto-generate a changelog from git commits by running this skill in your repository. It reads your commit history, parses conventional commit messages, and outputs a formatted changelog file grouped by entry type.

How does conventional commits format affect changelog generation?▼

Conventional commits standardize your messaging structure, allowing the changelog generator to accurately parse and group entries by type. This skill works best with conventional commits to automatically categorize features, fixes, docs, refactors, and tests.

Does this changelog generator include PR links in release notes?▼

Yes, this changelog generator includes PR links for each entry in the release notes. It automatically parses your git commit history and formats the output with grouped entries and their corresponding pull request links.

Do I need conventional commits to generate release notes?▼

You do not strictly need conventional commits to generate release notes, but they are highly recommended. This skill works best with conventional commits to successfully parse and group entries by type.

What is the best way to group git commits by type for release notes?▼

The best way to group git commits by type for release notes is using conventional commit messages. This skill automatically parses your commit history and groups entries into categories like feat, fix, docs, refactor, and tests.