Git changelog

Skill MasahiroSakoda/skills/skills/git-changelog

A collection of skills: Personal agentic workflows library

Install

npx -y skills add MasahiroSakoda/skills --skill git-changelog

Assembled from the repository path, not quoted from the project. Check it against their README if it does not work.

One thing to look at

0 stars0 stars. Stars are a popularity signal and not a quality one, but at this level it is likely that nobody has read this closely except its author, and you would be relying on your own review.

What its author says it does

Copied from the file, not written here

Generate changelog from current branch changes. Use when the user asks to write a changelog entry, fill the changelog section of a PR, or determine if changes are user-facing.

The file declares its own license as MIT. That is the author’s claim about this one file, and it is not the same thing as the license GitHub reports for the repository, which is listed with the other numbers below.

SKILL.md

3.3 KB, 742 tokens by cl100k_base, as published. Nobody here has run it

Changelog Generator

You are an AI assistant programmed to perform meticulous, context-aware changelog generations using the available tools. Your task is to analyze commit log and generate properly formatted changelog that follows the markdown format.

Command Execution Principle

Execute command exactly: Do not pipe the command unless explicitly requested.

Process Overview

Commit Log Analysis: Analyze the commit log with git command
Changelog Generation: Create changelog with commit message and extendable details

Changelog Workflows

Step 1: Check the Branches

Work on branches other than main or master. Otherwise, exit command with warning message.

DEFAULT_BRANCH=$(git remote show origin | grep 'HEAD branch' | awk '{print $NF}')
CURRENT_BRANCH=$(git branch --show-current)
if [ "$CURRENT_BRANCH" = "$DEFAULT_BRANCH" ]; then
  echo "🚨 On default branch — checkout branch first"
  exit 1
fi

Step 2: Commit Log Analysis

Get the commit log using git log $DEFAULT_BRANCH..$CURRENT_BRANCH

Step 3: Message Generation

Changelog Format

### Changelog

#### What's Changed

- Change summary #1
- Change summary #2
...

#### 🚨 Breaking Changes

<details>
<summary><type>(<scope>)!: <commit message> (<a href="commit link">commit hash</a>)</summary>

- Commit detail #1
- Commit detail #2
...
</details>

#### 🎉 New Features

<details>
<summary>feat(<scope>): <commit message> (<a href="commit link">commit hash</a>)</summary>

- Commit detail #1
- Commit detail #2
...
</details>

#### 🐞 Bug Fixes

<details>
<summary>fix(<scope>): <commit message> (<a href="commit link">commit hash</a>)</summary>

- Commit detail #1
- Commit detail #2
...
</details>

#### Other Changes

<details>
<summary><type>(<scope>): <commit message> (<a href="commit link">commit hash</a>)</summary>

- Commit detail #1
- Commit detail #2
...
</details>

Changelog Guidelines

What's changed: Summarize point of changes in "What's changed"
Breaking Changes: commit type contains type(scope)!
New Features: commit type: feat(scope):
Bug Fixes: commit type containsfix(scope)
Other Changes: Changes not belonging to the above items like chrore, refactor, docs.
Commit Details: Commit details should be separated by line breaks for each item.

Step 4: Quality Check

Before presenting the changelog, ensure:

Keep bullet points scannable (one line each) in "What's Changed"
Categorize commits where it should be.
Check the link for commit
Check the break new line for each commit details

Step 5: Paste changelog to clipboard

Paste suggested changelog to clipboard with OS-specific copy command (e.g.: pbcopy)

Output Format

Suggested changelog: in proper markdown format
Display execution result to paste to clipboard: Explain error details, if there are errors.

DO NOT change or write any files even draft. Your task is suggestion only.