changelog

Generate changelogs from git commits with ticket IDs.

Updated Feb 5, 2026

Search Tags:#automation #git #changelog #developer tools #commits #release notes

Ready to run

npx skills add https://github.com/SaintPepsi/brainstorm-pipeline --skill changelog-saintpepsi

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: changelog
Source: https://github.com/SaintPepsi/brainstorm-pipeline/tree/main/skills/changelog
Command: npx skills add https://github.com/SaintPepsi/brainstorm-pipeline --skill changelog-saintpepsi

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This Skill automates the creation of concise and informative changelogs by analyzing git commit history, saving developers time and ensuring consistent release notes.

Core Features & Use Cases

Automated Changelog Generation: Creates changelogs based on git commits.
Intelligent Formatting: Adapts output format (paragraph for bug fixes, sectioned bullets for features) based on commit count.
Base Branch Detection: Accurately identifies the correct base branch for comparison, even in complex merge scenarios.
Ticket ID Extraction: Parses branch names to identify associated ticket IDs.
Use Case: After completing a feature with multiple commits, use this Skill to generate a well-formatted changelog entry for the release notes.

Quick Start

Use the changelog skill to generate a changelog for the current branch.

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 commits automatically?▼

Automated release notes generation from git commits analyzes your current branch history to produce concise changelogs, detecting the base branch and extracting ticket IDs for accurate summarization.

Can I extract ticket IDs from branch names for my changelog?▼

Yes, extracting ticket IDs from branch names is supported during changelog generation. The process parses branch naming conventions to identify and link associated tickets in the release notes output.

How does automated changelog formatting adapt to different commit counts?▼

Changelog formatting adapts intelligently to commit counts by using paragraph formats for single bug fixes and sectioned bullet lists for multiple features, ensuring clear and concise release notes.

Does this changelog generator detect the correct base branch in complex merge scenarios?▼

Base branch detection works accurately even in complex merge scenarios. The generator identifies the correct comparison branch to ensure your changelog reflects only the relevant commit history.

What is the best way to create concise changelogs for feature branches with multiple commits?▼

The best way to create concise changelogs for feature branches is to analyze the commit history against the base branch, applying specific formatting rules for bug fixes and features to ensure clarity.