changelog-gen

Generate structured markdown changelogs from git commit history.

1|Updated Apr 13, 2026
One-click install
npx skills add https://github.com/0xjitsu/jitsu-skills --skill changelog-gen-0xjitsu
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: changelog-gen
Source: https://github.com/0xjitsu/jitsu-skills/tree/main/skills/changelog-gen
Command: npx skills add https://github.com/0xjitsu/jitsu-skills --skill changelog-gen-0xjitsu

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Generating accurate, structured changelog entries from git history is manual and error-prone; this skill automates parsing commits, categorizing changes, and producing release-ready markdown so maintainers don't assemble release notes by hand.

Core Features & Use Cases

  • Conventional commit parsing: Reads commits since the last tag, strips prefixes and scopes, capitalizes entries, and appends short hashes to produce clean sections.
  • AI fallback categorization: When conventional format is sparse, analyzes diffs and message content to classify commits into Added, Fixed, Changed, Documentation, Breaking Changes, and Internal.
  • Release integration: Prepends entries to CHANGELOG.md, creates a temporary CHANGELOG_ENTRY.md for gh/npm release workflows, and supports monorepo path filtering for package-scoped releases.

Quick Start

Generate a changelog entry for the current repository using conventional commit parsing, review the formatted entry, and then prepend it to CHANGELOG.md.

Frequently Asked Questions about changelog-gen

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

FAQPage Schema
How do I generate a changelog from git commit history?

This skill automates generating changelogs from git commit history by parsing commits since the last tag, categorizing them into sections like Added and Fixed, and outputting a formatted markdown changelog entry.

Can I generate release notes for a monorepo with path filtering?

Yes, you can generate release notes for a monorepo using optional path filtering to isolate package-scoped releases. This ensures the changelog only includes commits relevant to the specific package path being released.

How does AI fallback categorization work for unconventional commit messages?

When conventional commit format is insufficient, AI fallback categorization analyzes diffs and message content to classify commits into categories like Breaking Changes, Added, Fixed, Changed, Documentation, and Internal.

Do I need conventional commits to use this changelog generator?

No, you do not need conventional commits to use this changelog generator. It applies to repositories using conventional commits or mixed commit messages and falls back to AI-based categorization when the conventional format is sparse.

What is the best way to automate release notes for npm workflows?

The best way to automate release notes for npm workflows is to generate a temporary release file like CHANGELOG_ENTRY.md. This skill creates temporary files alongside prepending entries to CHANGELOG.md specifically for gh or npm release workflows.