core-changelog

Generate user-facing changelogs from conventional git commit history.

Updated Jan 1, 2026
One-click install
npx skills add https://github.com/AirMile/claude-config --skill core-changelog
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: core-changelog
Source: https://github.com/AirMile/claude-config/tree/main/skills/core-changelog
Command: npx skills add https://github.com/AirMile/claude-config --skill core-changelog

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Generate user-facing release notes from a project's git history by filtering noise, categorizing changes, and translating technical messages into customer-friendly language.

Core Features & Use Cases

  • Filter conventional commits (feat, fix, docs, style/cleanup, refactor, perf) to reduce noise and present end-user-facing summaries.
  • Automatically categorize changes into sections such as New Features, Improvements, and Bug Fixes, and translate messages for non-technical readers.
  • Use cases include preparing weekly release notes, publishing changelogs for customers, or maintaining internal change logs for stakeholders.

Quick Start

Run the /core-changelog skill to generate a changelog for the current repository.

Frequently Asked Questions about core-changelog

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

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

You can generate release notes from git history by running the skill against your repository, which extracts conventional commits, filters noise, categorizes changes, and translates them into user-friendly summaries.

How do conventional commits translate into a user-facing changelog?

Conventional commits are parsed and filtered by type, then automatically categorized into sections like New Features and Bug Fixes, and translated into user-friendly language for the changelog.

Can I format git changelog output as JSON instead of Markdown?

Yes, you can tailor the changelog output to render as either Markdown or JSON by passing the appropriate format arguments when invoking the generation process.

Does this changelog generator work with non-conventional git commits?

No, this tool applies specifically to projects using conventional commits. Non-conventional commit messages will not be properly filtered, categorized, or translated into user-friendly release notes.

How do I generate release notes for a specific git commit range?

You can generate a changelog for a specific git commit range by invoking the skill with an optional range argument, which resolves the boundary and extracts only the relevant commits.