Skip to content
TrustedSkillsbeta
Back to all skills

Changelog Automation

Checked
wshobson·vlatest·writing·MIT

Automatically generates concise, informative changelogs from commit messages, saving time and ensuring clarity for releases.

Repository

Install on your platform

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

  1. 1

    Run this in your project

    terminal
    $ npx skills add wshobson/agents --skill changelog-automation -a claude-code

  2. 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

wshobson

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

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 wshobson/agents at 46891e7e60.

    The exact upstream commit SHA that was scanned is recorded, so the result refers to specific bytes.

Commit
46891e7e60
Manifest
plugins/documentation-generation/skills/changelog-automation/SKILL.md
Scanned
2 files, 550 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

The changelog-automation skill enables AI agents to automatically generate and maintain changelogs for software projects. It parses version control systems like Git, extracts commit messages, and formats them into structured changelog entries following common standards such as Keep a Changelog.

When to use it

  • You need to keep your project's changelog up-to-date with every new release.
  • Your team uses Git and wants to automate the process of extracting meaningful changes from commits.
  • You're preparing for a software release and want a clean, well-formatted changelog ready for documentation or user communication.

Key capabilities

  • Parses commit messages from Git repositories
  • Groups changes by type (e.g., features, bug fixes)
  • Formats output according to Keep a Changelog conventions
  • Supports custom templates for changelog entries

Example prompts

  • "Generate a changelog for the latest release based on my Git commits."
  • "Format all recent feature additions and bug fixes into a markdown changelog."
  • "Create a changelog entry using the 'feat' type for the commit with hash abc1234."

Tips & gotchas

  • Ensure your Git repository is properly configured with meaningful commit messages.
  • This skill relies on access to version control history, so it may not work without proper repository permissions or setup.