Skip to content
TrustedSkillsbeta
Back to all skills

Changelog Generator

Checked
davepoon·vlatest·writing·MIT

This tool automatically creates detailed changelogs from code commits, saving developers time and ensuring clear release 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 davepoon/buildwithclaude --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

davepoon

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 davepoon/buildwithclaude at fc03a95b41.

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

Commit
fc03a95b41
Manifest
plugins/all-skills/skills/changelog-generator/SKILL.md
Scanned
1 file, 94 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 structured changelogs for software projects. It takes raw commit messages or release notes and formats them into a clean, readable document suitable for public distribution.

When to use it

  • You have a repository with many commits but no time to manually write release notes.
  • You need to standardize the format of changelogs across multiple team members.
  • You want to quickly summarize recent updates for documentation or marketing materials.
  • You are preparing a release and need to categorize changes (e.g., features, bug fixes) automatically.

Key capabilities

  • Parses raw commit history or unstructured text input.
  • Generates formatted changelog entries with clear headers.
  • Organizes updates into logical sections based on content type.
  • Produces output ready for copy-pasting into README files or release pages.

Example prompts

  • "Generate a changelog for my latest release using these commit messages: [paste commits]."
  • "Create a formatted changelog summarizing the following update notes: [paste notes]."
  • "Draft a release note section highlighting new features and bug fixes from this log: [paste log]."

Tips & gotchas

Ensure your input includes clear descriptions of changes; vague commit messages may result in generic output. This tool is best suited for technical summaries rather than marketing-heavy copy, so review the generated text to add tone or flair if needed.