Skip to content
TrustedSkillsbeta
Back to all skills

Changelog Updater

Checked
u9401066·vlatest·writing·Apache-2.0

This skill automatically generates a detailed changelog from code commits, saving developers time and ensuring clear release notes.

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 u9401066/med-paper-assistant --skill changelog-updater -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

u9401066

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 u9401066/med-paper-assistant at 7e1eab0b05.

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

Commit
7e1eab0b05
Manifest
.claude/skills/changelog-updater/SKILL.md
Scanned
1 file, 38 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-updater skill automatically generates and formats changelog entries based on provided commit messages. It parses commit history, extracts relevant information like author, date, and message, and structures this data into a standardized changelog format (e.g., Conventional Commits). This simplifies the process of maintaining accurate and up-to-date project documentation.

When to use it

  • Software Development: Quickly generate changelogs for new releases based on Git commit history.
  • Open Source Projects: Maintain a clear record of changes for contributors and users.
  • Documentation Updates: Automatically update release notes or other documentation that relies on changelog information.
  • Automated Release Pipelines: Integrate into CI/CD pipelines to automatically generate changelogs as part of the release process.

Key capabilities

  • Parses Git commit messages
  • Extracts author, date, and message from commits
  • Formats output in a standardized changelog format (Conventional Commits)
  • Generates changelog entries based on commit history

Example prompts

  • "Generate a changelog for the last 5 releases."
  • "Create a changelog entry from this commit: 'Fix: Resolved issue with data validation.'"
  • "Update the changelog with all commits since version 1.2.0."

Tips & gotchas

  • Requires access to a Git repository or commit history.
  • The quality of the generated changelog depends on well-formatted and descriptive commit messages.