Code Changelog

Name: Code Changelog
Author: bear2u

Checked

bear2u·vlatest·writing

Generates a detailed code changelog from commit messages, streamlining documentation and improving project understanding.

Repository

Install on your platform

Showing Claude Code. One command installs this skill into any of the agents below.

Run this in your project

terminal

$ npx skills add bear2u/my-skills --skill code-changelog -a claude-code

Uses the open-source skills CLI and needs Node.js. Add -g to install it for your user instead of this project.

What we know about this skill

Publisher

bear2u

Taken from the source listing. We haven't verified who controls this account.

Install target

Live repository

Not pinned. Installing fetches whatever the repository holds at the time you run the command.

No human has reviewed this code. The checks below are a static scan of the files at one commit — nobody has run this skill or judged whether it works. A skill runs with whatever access you give your agent, so read the source before you install it.

Automated safety checks

scanned 28 Sept 2026

This skill passed all 6 checks. We read its files at one commit and looked for the things that make a skill dangerous to run — not for whether it works.

Declares what it does: passed
SKILL.md parses and declares a name and a description.
SKILL.md exists, its frontmatter parses, and it declares a name and a description.
No undeclared network calls: passed
Makes no network calls.
Every host the skill dials — from its scripts, its config endpoints or the commands it tells the agent to run — is either well-known package and API infrastructure or declared in its own frontmatter. Links in documentation are not counted.
No obfuscated payloads: passed
No encoded or obfuscated payloads.
No base64, hex or compressed blob is decoded and then executed, and no encoded shell commands.
No credential access: passed
Reads no keys, tokens, keychains or credential files.
Neither the code nor the SKILL.md instructions read SSH keys, cloud credentials, keychains, token stores, browser cookie databases or dotfiles that hold secrets.
No pipe-to-shell installers: passed
No pipe-to-shell or download-and-run installers.
No `curl … | sh` pattern, in the code or in the instructions, that runs code fetched at run time.
Pinned to a commit: passed
Scanned bear2u/my-skills at 8ed5784784.
The exact upstream commit SHA that was scanned is recorded, so the result refers to specific bytes.

Commit: 8ed5784784
Manifest: skills/code-changelog/SKILL.md
Scanned: 2 files, 350 lines

This is a static scan, not a review. It reads the skill's files; it does not run them, and it cannot tell you whether the skill is any good or whether the code does what its description says. A skill runs with whatever access you give your agent.

What each check looks for →

About this skill

What it does

This skill generates changelogs from commit messages. It parses a repository's history, extracts relevant information from commit messages, and formats this into a human-readable changelog document. The resulting changelog can be used for release notes or internal documentation.

When to use it

You need to quickly create release notes from a Git repository.
You want to automate the process of documenting changes in a software project.
Your team follows consistent commit message conventions that can be parsed for meaningful change summaries.
You're preparing for a new version and require a consolidated view of recent modifications.

Key capabilities

Parses Git repository history.
Extracts information from commit messages.
Formats extracted data into changelog documents.

Example prompts

"Generate a changelog for the my-project repository."
"Create release notes based on commits since tag 'v1.0'."
“Summarize changes in the last month from the main branch.”

Tips & gotchas

The quality of the generated changelog depends heavily on well-formatted and consistent commit messages. Ensure your team adheres to a clear commit message convention for optimal results.