Skip to content
TrustedSkillsbeta
Back to all skills

Changelog

Checked
johnlindquist·vlatest·writing

The Changelog skill generates concise, informative release notes summarizing changes, streamlining documentation and improving 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 johnlindquist/claude --skill changelog -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

johnlindquist

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 johnlindquist/claude at eb37d88225.

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

Commit
eb37d88225
Manifest
skills/changelog/SKILL.md
Scanned
1 file, 228 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, johnlindquist-changelog, allows AI agents to generate and format changelogs. It can parse commit messages from a Git repository and transform them into human-readable release notes. The resulting changelog includes details like version numbers, dates, and descriptions of changes made in each commit.

When to use it

  • Generating Release Notes: Automatically create changelogs for software releases based on Git commit history.
  • Summarizing Project Activity: Quickly understand the evolution of a project by generating a summary of recent changes.
  • Documenting API Updates: Produce clear and concise documentation outlining modifications to an API.
  • Creating User-Facing Change Logs: Produce changelogs suitable for distribution to end users, explaining new features or bug fixes.

Key capabilities

  • Parses Git commit messages.
  • Formats output into a human-readable changelog.
  • Includes version numbers and dates in the generated changelog.
  • Provides descriptions of changes made in each commit.

Example prompts

  • "Generate a changelog for this repository."
  • "Create a release notes document from the last 10 commits."
  • "Summarize the changes between version 1.0 and 2.0."

Tips & gotchas

  • The skill relies on accurate and well-formatted commit messages in the Git repository for optimal results. Poorly written commit messages will lead to a less informative changelog.