changelog

Generate dated Mintlify MDX changelog entries from git history.

Updated Aug 23, 2026
One-click install
npx skills add https://github.com/Bolivar1234/qwntik-fabro --skill changelog-bolivar1234
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: changelog
Source: https://github.com/Bolivar1234/qwntik-fabro/tree/main/.claude/skills/changelog
Command: npx skills add https://github.com/Bolivar1234/qwntik-fabro --skill changelog-bolivar1234

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

Changelog management is often manual and error-prone. This skill automates extracting user-facing changes from git history and publishes MDX entries for Mintlify docs, ensuring release notes stay accurate and up to date.

Core Features & Use Cases

  • Automated date-based grouping: aggregates commits by date and filters to user-facing changes (features, fixes, breaking changes, and provider updates).
  • MDX generation & publishing: writes dated MDX entries to docs/public/changelog/ and updates docs/public/docs.json for site navigation.
  • Incremental runs with watermark: tracks the last processed commit using a watermark to avoid reprocessing and support continuous publishing.

Quick Start

Run the changelog skill to generate the latest user-facing changelog entries from main and publish them to the docs directory.

Frequently Asked Questions about changelog

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

FAQPage Schema
How do I auto-generate changelog entries from git history?

To auto-generate changelog entries from git history, a skill analyzes your main branch commits, filters for user-visible changes like features and fixes, and groups them by date to create dated release notes.

Can I publish release notes directly to Mintlify MDX files?

Yes, you can publish release notes to Mintlify MDX files by writing dated entries to the docs/public/changelog/ directory and updating the docs.json file to configure site navigation.

How do I prevent duplicate changelog generation when processing git commits?

To prevent duplicate changelog generation, the skill maintains a watermark file at .claude/skills/changelog/watermark to track the last processed commit, ensuring incremental runs avoid reprocessing.

What types of user-facing changes are extracted for documentation?

The changelog extraction filters git history for user-visible changes including new features, bug fixes, breaking changes, and provider updates to include in the documentation.

Does this changelog automation require a specific git branch structure?

Yes, the changelog automation requires analyzing the main branch history specifically, as it surfaces user-visible changes by grouping commits from main into daily MDX entries.