Skip to content
TrustedSkillsbeta
Back to all skills

Leather Changelog

Checked
leather-io·vlatest·writing·MIT

Leather Changelog generates detailed, human-readable changelogs from code commits, streamlining documentation and improving transparency for software projects.

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 leather-io/mono --skill leather-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

leather-io

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 leather-io/mono at 8d34d406cc.

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

Commit
8d34d406cc
Manifest
.claude/skills/leather-changelog/SKILL.md
Scanned
3 files, 777 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 leather-changelog skill provides a structured way to generate changelogs from commit messages. It parses Git history, extracts relevant information from commit messages, and formats it into a human-readable changelog document. This allows for easy tracking of changes over time and clear communication with users or stakeholders.

When to use it

  • Generating release notes: Automatically create release notes based on your project's commit history.
  • Documenting software updates: Produce a concise record of changes made in each version of your software.
  • Communicating with clients/users: Share clear and informative changelogs to keep users informed about new features and bug fixes.
  • Maintaining project transparency: Provide an accessible history of development efforts for internal teams or open-source contributors.

Key capabilities

  • Parses Git commit messages
  • Extracts information from commits
  • Formats output into a changelog document

Example prompts

  • "Generate a changelog for the last three releases."
  • "Create a changelog summarizing all changes in the 'feature-branch' branch."
  • "Output a changelog formatted as Markdown, including commit authors."

Tips & gotchas

  • Requires access to a Git repository. The quality of the generated changelog depends heavily on well-formatted and descriptive commit messages.