Git Commit to Changelog Markdown Mapper

Turn messy Git history into release notes people can actually read

Writing release notes by manually scanning dozens or hundreds of commits is repetitive, error-prone, and easy to postpone.

Git Commit to Changelog Markdown Mapper reads your local repository history between two refs, removes merge and configurable automation noise, categorizes each relevant change, and generates clean Markdown with commit-level traceability.

• Reads Git history directly from the local repository
• Supports tags, branches, commits and HEAD revision ranges
• Excludes merge commits automatically
• Supports configurable automation and bot filters
• Understands common Conventional Commit prefixes
• Uses conservative fallback classification for unstructured messages
• Creates Features, Fixes, Performance, Improvements, Documentation, Tests and Maintenance sections
• Retains source commit hashes for traceability
• Generates a companion traceability JSON file
• Records excluded commits separately
• Never rewrites Git history, rebases, tags or pushes

Why use this instead of normal ChatGPT?

The Skill reads the real local Git history through the Git CLI, processes the complete revision range, and writes the release artifact directly into the repository without requiring private commit history to be copied into a browser chat.

Git Range → Filter → Categorize → Normalize → release_notes.md

Traceable by design

Every generated release-note entry remains linked to its source commit hash. Ambiguous commit messages are kept conservative rather than being embellished with unsupported claims.