Skip to content
TrustedSkillsbeta
Back to all skills

Changelog Generator

Checked
matteocervelli·vlatest·writing·MIT

Automatically creates detailed changelogs from code commits, streamlining updates and improving transparency for developers and users.

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 matteocervelli/llms --skill changelog-generator --full-depth -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

matteocervelli

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 matteocervelli/llms at 1e1f2089eb.

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

Commit
1e1f2089eb
Manifest
.archive/claude-v1/skills/changelog-generator/SKILL.md
Scanned
1 file, 642 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 automatically generates changelogs based on provided commit messages. It parses a list of commits, extracts relevant information, and formats it into a human-readable changelog document suitable for release notes or similar purposes. The generated changelog includes details like version numbers, descriptions, and potentially other metadata derived from the commit history.

When to use it

  • Software Releases: Quickly create changelogs when releasing new versions of software projects.
  • Project Documentation: Automatically update project documentation with a record of changes.
  • Internal Communication: Generate summaries of development activity for team updates or stakeholders.
  • Automated Reporting: Integrate into CI/CD pipelines to automatically produce release notes.

Key capabilities

  • Parses commit messages.
  • Extracts information from commits.
  • Formats output as a changelog document.

Example prompts

  • "Generate a changelog from these commit messages: [paste commit messages here]"
  • "Create a release note for version 1.2.3 based on the following commits: [paste commit messages here]"
  • “Summarize changes in this repository's history into a changelog.”

Tips & gotchas

The quality of the generated changelog depends heavily on the clarity and consistency of your commit messages. Ensure that commit messages follow a standardized format for optimal results.