changelog

Generate changelog entries from git commits using Conventional Commits.

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

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) and references (resource) components.

What problem does it solve?

This Skill automates the creation of changelog entries by parsing Git commits, ensuring your project's release notes are consistently and accurately documented.

Core Features & Use Cases

  • Automated Changelog Generation: Creates changelog entries based on Conventional Commits.
  • Style Detection & Matching: Analyzes existing CHANGELOG.md to match its style (sections, bullets, dates, etc.).
  • Commit Enhancement: Improves vague commit messages by analyzing code diffs for context.
  • Fallback to Raw Git: Works even if the Chronicle CLI is not installed, using standard Git commands.
  • Use Case: After a development sprint, use this Skill to generate the release notes for the new version, ensuring all significant changes are captured and formatted correctly.

Quick Start

Generate the changelog for the latest release.

Frequently Asked Questions about changelog

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

FAQPage Schema
How do I automate changelog generation from git commits?

To automate changelog generation from git commits, this Skill parses commit history using the Conventional Commits specification to compile and format release notes. It analyzes existing CHANGELOG.md files to match your current documentation style.

What is the Conventional Commits specification for release notes?

The Conventional Commits specification provides a standardized format for commit messages that maps to semantic versioning. This Skill uses it to parse commit types and generate structured changelog entries.

How do I generate a changelog if my project doesn't use Conventional Commits?

To generate a changelog for non-conventional commit projects, this Skill handles edge cases by providing fallback mechanisms and user feedback options. It enhances vague commit descriptions by analyzing code diffs for context.

Do I need the Chronicle CLI installed to generate release notes?

You do not need the Chronicle CLI installed to generate release notes, as the Skill provides a fallback to raw Git commands. This ensures changelog generation works in environments without the Chronicle CLI dependency.

How do I match new changelog entries to an existing CHANGELOG.md style?

To match new changelog entries to an existing CHANGELOG.md style, the Skill performs automated style detection by analyzing your current file's sections, bullets, and dates. It formats generated entries to maintain consistency.

Can I improve vague git commit messages when generating documentation?

You can improve vague git commit messages during documentation generation, as the Skill enhances ambiguous descriptions by analyzing actual code diffs. This extracts context to produce accurate changelog entries.