Skip to content
TrustedSkillsbeta
Back to all skills

Changelog Generator

Checked
decebals·vlatest·writing·MIT

This tool automatically creates detailed changelogs from code commits, saving developers time and ensuring clear project history documentation.

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 decebals/claude-code-java --skill changelog-generator -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

decebals

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 decebals/claude-code-java at 0d98fe9bd6.

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

Commit
0d98fe9bd6
Manifest
skills/changelog-generator/SKILL.md
Scanned
2 files, 345 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 decebals-changelog-generator skill automatically generates changelogs from commit messages. It parses a repository's commit history and formats it into a human-readable changelog document, suitable for release notes or internal documentation. This reduces manual effort in summarizing project changes.

When to use it

  • Preparing for releases: Quickly create a changelog to accompany a new software version.
  • Documenting project evolution: Maintain an ongoing record of changes made to a codebase.
  • Generating release notes: Automatically populate release notes with concise summaries of commits.
  • Internal team communication: Provide a clear overview of recent development activity for internal stakeholders.

Key capabilities

  • Parses commit messages from Git repositories.
  • Formats parsed data into changelog entries.
  • Supports various output formats (implied, not explicitly stated).

Example prompts

  • "Generate a changelog for the my-project repository."
  • "Create a release notes document based on commits since tag 'v1.0'."
  • "Summarize changes in the last month for project awesome-tool."

Tips & gotchas

The quality of the generated changelog depends heavily on well-formatted and descriptive commit messages. Ensure your team follows consistent commit message conventions for optimal results.