Skip to content
TrustedSkillsbeta
Back to all skills

Changelog

Checked
itechmeat·vlatest·writing·MIT

The Changelog skill generates detailed release notes summarizing changes, boosting transparency and developer understanding of software updates.

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 itechmeat/llm-code --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

itechmeat

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 itechmeat/llm-code at 7ae8a00524.

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

Commit
7ae8a00524
Manifest
skills/changelog/SKILL.md
Scanned
3 files, 412 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 Changelog skill generates release notes formatted according to the Keep a Changelog specification and Semantic Versioning (SemVer). It structures changes into sections like "Added," "Changed," "Fixed," and others, providing a clear record of software updates for developers and users. All content must be written in English.

When to use it

  • To automatically generate release notes for software projects following SemVer or date-based versioning.
  • When needing to maintain a detailed history of changes made to a project.
  • For teams that prioritize transparency and developer understanding of updates.
  • To ensure consistent formatting of changelog entries based on established standards.

Key capabilities

  • Generates changelogs formatted according to Keep a Changelog.
  • Supports Semantic Versioning (SemVer) and date-based versioning.
  • Organizes changes into categories like "Added," "Changed," "Fixed," "Deprecated," "Removed," and "Security."
  • Enforces English language for all changelog content, requiring translation of any source information provided in other languages.

Example prompts

  • "Generate a changelog entry for version 1.2.3 including a new feature called 'Improved Search'."
  • "Create a changelog section for bug fixes in the latest release."
  • "Format this change description as a 'Changed' entry: 'Refactored authentication module.'"

Tips & gotchas

  • All content must be written in English. The skill will not generate entries in other languages.
  • The skill adheres to strict formatting rules based on the Keep a Changelog specification, so ensure your prompts align with these guidelines for best results.
  • Date-based versioning is supported as an alternative to SemVer.