Skip to content
TrustedSkillsbeta
Back to all skills

Changelog Generator

Checked
jst-well-dan·vlatest·writing

This skill automatically creates detailed changelogs from project updates, saving time and ensuring clear communication of changes.

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 jst-well-dan/skill-box --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

jst-well-dan

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 jst-well-dan/skill-box at 935be9cae6.

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

Commit
935be9cae6
Manifest
dev-tools/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 generates changelogs. It takes a description of changes as input and formats them into a standard changelog format, suitable for software releases or project updates. The generated changelog can be easily incorporated into documentation or release notes.

When to use it

  • You've just completed a development sprint and need to quickly document the changes made.
  • Preparing release notes for a new version of your software or product.
  • Creating a summary of updates for internal team communication.
  • Automating the changelog creation process as part of a CI/CD pipeline.

Key capabilities

  • Generates changelogs from input descriptions.
  • Formats output into a standard changelog structure.
  • Suitable for software releases and project updates.

Example prompts

  • "Generate a changelog for these changes: Fixed bug in user authentication, added support for dark mode, improved performance of data loading."
  • “Create a changelog based on this description: Refactored the payment processing module to improve security.”
  • "Produce a changelog from the following updates: Implemented new API endpoint for retrieving customer data, updated dependencies to latest versions."

Tips & gotchas

The quality of the generated changelog depends heavily on the clarity and detail provided in the input description. Ensure you provide sufficient context for accurate and informative entries.