changelog

Generate structured changelogs from git commit history by conventional commit types.

Updated Mar 9, 2026
One-click install
npx skills add https://github.com/bswrundquist/devtools --skill changelog-bswrundquist
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: changelog
Source: https://github.com/bswrundquist/devtools/tree/main/src/devtools/templates/claude/user/.claude/skills/changelog
Command: npx skills add https://github.com/bswrundquist/devtools --skill changelog-bswrundquist

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill requires gh, and includes scripts (resource) and references (resource) components.

What problem does it solve?

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

Core Features & Use Cases

  • Automated Commit Parsing: Groups commits by conventional commit types (feat, fix, chore, etc.).
  • PR Integration: Optionally integrates with GitHub CLI to link pull requests.
  • Breaking Change Highlighting: Clearly identifies and surfaces breaking changes.
  • Use Case: After merging a feature branch into main, use this Skill to generate a changelog entry detailing the new features, fixes, and any breaking changes introduced since the last release tag.

Quick Start

Generate a changelog for commits between the last tag and the current HEAD.

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 commit history?

Generate a changelog from git commit history by parsing commits between specified tags, branches, or SHAs and grouping them by conventional commit types. This Skill automates that parsing to produce structured release notes.

What are conventional commits and how do they structure release notes?

Conventional commits use prefixes like feat, fix, and chore to categorize changes in git history. This Skill parses these conventional commit types to group commits and structure your changelog entries automatically.

Can I link GitHub pull requests to my changelog entries?

Link GitHub pull requests to your changelog entries by integrating with the GitHub CLI. This Skill optionally uses the gh CLI to fetch and append PR links directly into the generated release notes.

Do I need the GitHub CLI installed to generate changelogs?

The GitHub CLI is required only if you want to enable PR linking in your changelog. Git is required for basic commit parsing, but the gh CLI is an optional dependency needed for full functionality.

How do I highlight breaking changes in release notes?

Highlight breaking changes in release notes by parsing git history for specific conventional commit flags. This Skill identifies and clearly surfaces breaking changes at the top of the generated changelog.

Can I generate a changelog between two specific git tags or branches?

Generate a changelog between two specified git tags, branches, or commit SHAs. This Skill parses the commit history within those exact boundaries to output a structured changelog for that specific range.