Skip to content
TrustedSkillsbeta
Back to all skills

Release Changelog

Checked
7up-ai·vlatest·writing

Automatically generates a detailed changelog from your code commits, streamlining documentation and improving team collaboration in DevOps workflows.

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 7up-ai/coding-skill --skill release-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

7up-ai

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 7up-ai/coding-skill at 1ed88147c8.

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

Commit
1ed88147c8
Manifest
skills/release-changelog/SKILL.md
Scanned
2 files, 313 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 generates a release changelog based on provided commit messages. It can summarize changes, categorize them by type (features, bug fixes, etc.), and format the output in Markdown or other specified formats. The tool aims to automate the creation of release notes for software projects.

When to use it

  • You need to quickly generate release notes from a repository's commit history.
  • You want to automatically categorize changes into features, bug fixes, and improvements.
  • You are preparing a new version of your software and require a formatted changelog document.
  • You want to streamline the process of communicating changes to users or stakeholders.

Key capabilities

  • Generates release changelogs from commit messages.
  • Categorizes commits (e.g., features, bug fixes).
  • Formats output in Markdown or other formats.
  • Summarizes changes for a concise overview.

Example prompts

  • "Generate a release changelog for the 'my-project' repository."
  • "Create a Markdown changelog from the last 10 commits of the 'feature-branch'."
  • "Summarize the changes in the 'release/v1.2' branch and format as a bulleted list."

Tips & gotchas

  • The quality of the generated changelog depends heavily on the clarity and consistency of your commit messages. Well-formatted commit messages are essential for accurate categorization and summarization.