Skip to content
TrustedSkillsbeta
Back to all skills

Changelog Writer

Checked
peopleforrester·vlatest·writing·MIT

Generates clear, concise changelogs summarizing software updates and improvements – boosting transparency & user understanding.

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 peopleforrester/claude-dotfiles --skill changelog-writer -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

peopleforrester

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 peopleforrester/claude-dotfiles at db7caa0374.

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

Commit
db7caa0374
Manifest
skills/documentation/changelog-writer/SKILL.md
Scanned
1 file, 233 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 changelog entries from provided commit messages. It can parse common git formats and produce structured output suitable for various changelog formats (e.g., Markdown, reStructuredText). The resulting changelog entries are formatted with clear headings and descriptions based on the commit message content.

When to use it

  • Automating repetitive tasks: Quickly generate changelogs for software releases without manual effort.
  • Maintaining consistent formatting: Ensure all changelog entries adhere to a defined style guide.
  • Creating release notes: Produce comprehensive release notes by automatically extracting information from commit history.
  • Documenting project changes: Keep an accurate record of modifications and improvements made throughout the development lifecycle.

Key capabilities

  • Parses Git commit messages.
  • Formats changelog entries in Markdown or reStructuredText.
  • Supports common Git formats.
  • Generates structured output.

Example prompts

  • "Generate a changelog from these commit messages: [paste commit messages here]"
  • "Create a markdown changelog for the last release, using standard headings."
  • “Summarize the changes in this git repository into a changelog.”

Tips & gotchas

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