changelog

Generate dated MDX changelog entries from Git history.

1.5k|159|Updated Mar 13, 2026
One-click install
npx skills add https://github.com/fabro-sh/fabro --skill changelog-fabro-sh
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: changelog
Source: https://github.com/fabro-sh/fabro/tree/main/.claude/skills/changelog
Command: npx skills add https://github.com/fabro-sh/fabro --skill changelog-fabro-sh

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

Automatically generate and update product changelogs in Mintlify docs by deriving user-facing changes from Git history.

Core Features & Use Cases

  • Reads git history on main to identify user-facing changes.
  • Writes dated MDX changelog entries to docs/public/changelog/.
  • Supports release notes and documentation workflows for product teams.

Quick Start

Run the changelog skill to extract recent user-facing changes and publish them as MDX entries in docs/public/changelog.

Frequently Asked Questions about changelog

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

FAQPage Schema
How do I generate release notes from Git history automatically?

To generate release notes from Git history automatically, this Skill reads your repository main branch commits and writes dated MDX changelog entries to your docs directory. It extracts user-facing changes across features, bug fixes, and improvements.

How does automated changelog generation work for MDX documentation?

Automated changelog generation for MDX works by reading Git commit history on the main branch and maintaining a watermark to avoid reprocessing. It then writes dated MDX files to the docs/public/changelog/ directory for your product documentation.

Can I use this to generate Mintlify docs changelogs from my main branch?

Yes, you can generate Mintlify docs changelogs from your main branch. The Skill depends on your repository main branch history to automatically derive and publish user-facing changes as dated MDX entries.

Do I need a specific Git branch structure to auto-generate changelog MDX files?

You need a Git repository with a main branch to auto-generate changelog MDX files. The Skill specifically reads commit history from the main branch and maintains a progress watermark to avoid duplicating previously processed commits.

What is the best way to automate release notes for product documentation?

The best way to automate release notes for product documentation is to extract changes directly from Git history. This Skill identifies features, bug fixes, and improvements from commits and writes them as dated MDX files to your docs/public/changelog/ folder.

How does the changelog generator avoid duplicating already processed commits?

The changelog generator avoids duplicating processed commits by maintaining a progress watermark. This mechanism tracks previously read Git history on the main branch, ensuring only new user-facing changes are extracted into MDX changelog entries.