Skip to content
TrustedSkillsbeta
Back to all skills

Changelog Generator

Checked
eyadsibai·vlatest·writing

Automatically creates detailed changelogs from code commits, streamlining documentation and improving collaboration 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 eyadsibai/ltk --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

eyadsibai

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 eyadsibai/ltk at f8e85697b9.

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

Commit
f8e85697b9
Manifest
plugins/ltk-github/skills/changelog-generator/SKILL.md
Scanned
1 file, 114 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 eyadsibai-changelog-generator skill automatically generates a formatted changelog from commit messages. It analyzes Git history, extracts relevant information from commit messages, and structures it into a human-readable changelog document. This simplifies the process of creating release notes and documenting project changes.

When to use it

  • Generating Release Notes: Quickly create a well-formatted changelog for software releases based on your Git commit history.
  • Documenting Project Changes: Maintain an ongoing record of modifications and improvements made to a codebase.
  • Automating Changelog Updates: Integrate into CI/CD pipelines to automatically update the changelog with each new release.
  • Creating User-Facing Documentation: Produce clear and concise documentation for users outlining changes in a project.

Key capabilities

  • Parses Git commit messages.
  • Formats output as a changelog document.
  • Supports automated generation.

Example prompts

  • "Generate a changelog from the last 10 commits."
  • "Create a changelog for version 2.0, based on all commits since version 1.0."
  • “Format this commit history into a changelog: [paste commit history here]”

Tips & gotchas

  • Ensure your Git commit messages follow a consistent and informative format for optimal results. The quality of the generated changelog depends heavily on well-written commit messages.