changelog

Parse git commit history to generate Keep a Changelog entries.

8|1|Updated Mar 28, 2026
One-click install
npx skills add https://github.com/bostonaholic/team --skill changelog-bostonaholic
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: changelog
Source: https://github.com/bostonaholic/team/tree/main/skills/changelog
Command: npx skills add https://github.com/bostonaholic/team --skill changelog-bostonaholic

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This skill solves the problem of maintaining a clear, user-focused project history by automatically filtering technical commit noise and translating developer-centric messages into plain-language updates.

Core Features & Use Cases

  • Commit Filtering: Automatically ignores internal chores, tests, and refactors while highlighting user-facing features and security fixes.
  • Standardized Formatting: Enforces Keep a Changelog conventions to ensure consistency across project releases.
  • Use Case: When preparing for a new release, use this skill to scan your recent git history and generate a clean, professional summary of changes that users will actually care about.

Quick Start

Run the changelog skill to scan recent commits and update the Unreleased section of your project changelog file.

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?

You can generate a changelog from git commit history by parsing repository logs and filtering for user-visible changes. This process translates developer-centric messages into plain-language updates categorized by impact and type.

How do I filter internal chores and refactors out of my release notes?

To filter internal chores and refactors from release notes, apply semantic commit message filtering to your git history. This automatically ignores technical commit noise while highlighting user-facing features and security fixes for your documentation.

Does Keep a Changelog formatting work with automated git parsing?

Keep a Changelog formatting works with automated git parsing by enforcing standardized conventions for consistency across project releases. The parsed git commits are categorized and inserted into the Unreleased section to maintain a clear project history.

What's the best way to maintain a human-readable project changelog for a new release?

The best way to maintain a human-readable project changelog is to scan recent git history and filter technical commit noise automatically. This ensures you generate a clean, professional summary of changes that users actually care about for the release.

Do I need semantic commit messages to automate my project changelog?

You need semantic commit messages to automate your project changelog because the process relies on semantic commit message filtering. This requirement ensures high-quality documentation by accurately categorizing user-facing features and security fixes.