Skip to content
TakoAPI
Back to skills

git-changelog

by fratua

Git & GitHub
581Downloads reported by clawskills.sh
0Views
0 likesSign in to like this skill
—Not yet rated
Your rating

Brief

Auto-generate beautiful changelogs from git history, grouped by conventional commit types.

Description

What This Skill Does

Reads git commit history and produces a categorized, markdown-formatted changelog grouped by conventional commit types. Handles tag ranges, date ranges, and breaking change detection automatically. Output is ready to paste into CHANGELOG.md or a GitHub release.

Parsing conventional commits and grouping them by type by hand is tedious and error-prone, especially across long ranges; this skill automates the whole process in one step.

When to Use It

  • Generating release notes before tagging a new version
  • Creating a CHANGELOG.md entry after a sprint
  • Reviewing what changed between two git tags
  • Catching breaking changes before publishing a package
  • Summarizing recent commits for a team update

Example Workflow

INPUT

User asks: generate a changelog from v1.1.0 to HEAD

AGENT
  1. 1

    Verify the current directory is a git repository using git rev-parse

  2. 2

    Determine the commit range from v1.1.0 to HEAD

  3. 3

    Extract commits with hash, subject, author, and date using git log

  4. 4

    Parse each commit subject for conventional commit prefixes and group into categories

  5. 5

    Check for BREAKING CHANGE footers and feat! commits, then render the full markdown output

OUTPUT

A markdown changelog with sections for Features, Bug Fixes, and any other detected categories, including short commit hashes and scopes

Installation

clawhub install fratua/git-changelog

Run the CLI command, or paste the prompt into Claude Code, Cursor, Codex or whichever coding agent you use.

Links