changelog

Generate a Markdown changelog from branch-to-main git history.

6|1|Updated Mar 30, 2026

Search Tags:#git #changelog #documentation #pull request #release notes #change classification #diff summary

Ready to run

npx skills add https://github.com/wesleyosantos91/multi-agents --skill changelog-wesleyosantos91

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: changelog
Source: https://github.com/wesleyosantos91/multi-agents/tree/main/devin/.devin/skills/changelog
Command: npx skills add https://github.com/wesleyosantos91/multi-agents --skill changelog-wesleyosantos91

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

It solves the problem of manually writing inconsistent, time-consuming changelogs by turning branch-to-main git history into a structured summary of changes.

Core Features & Use Cases

Collects branch commits and file diffs: gathers commit summaries and per-file statistics for main...HEAD comparisons.
Classifies change types: groups work into feat, fix, refactor, docs, test, infra, deps, and breaking categories.
Produces a PR/release-ready Markdown format: outputs a consistent changelog template that’s easy to scan and reuse.

Quick Start

Ask the AI to generate a changelog comparing the current branch (HEAD) to main and format it as a Markdown sectioned summary.

Frequently Asked Questions about changelog

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

FAQPage Schema

How do I generate a changelog from git branch diffs automatically?▼

You can generate a changelog by comparing the current branch history against main, summarizing commits and changed files into categorized change types like Features, Fixes, and Breaking Changes for Markdown output.

What is the best way to create release notes from git commit history?▼

Creating release notes from git commit history involves classifying commit summaries and per-file statistics into structured categories, producing a Markdown changelog grouped by Features, Fixes, Refactors, and Breaking Changes.

Can I classify git commits into features, fixes, and breaking changes for a PR?▼

Yes, you can classify git commits into features, fixes, refactors, and breaking changes for PR workflows by evaluating git log and git diff outputs against main, producing a categorized Markdown summary.

Do I need git log and git diff outputs to generate a structured changelog?▼

Yes, you need git log and git diff outputs to generate a structured changelog, as these provide the commit summaries and per-file statistics required to classify changes and produce the final Markdown documentation.

How to format pull request documentation with categorized change types in Markdown?▼

Format pull request documentation by grouping branch-to-main file diffs and commit summaries into categorized change types, outputting a consistent, scannable Markdown changelog template for release and PR workflows.