Skip to content
TrustedSkillsbeta
Back to all skills

Changelog

Checked
sgcarstrends·vlatest·writing·MIT

Generates detailed changelogs for software projects, streamlining updates and improving user communication by clearly outlining modifications.

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 motormetrics/motormetrics --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

sgcarstrends

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 sgcarstrends/sgcarstrends at d852d8c519.

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

Commit
d852d8c519
Manifest
.agents/skills/changelog/SKILL.md
Scanned
2 files, 118 lines
Copies in repo
2 — all of them scanned
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 automates the generation of detailed changelogs for software projects using @semantic-release/changelog. It leverages commit messages formatted according to conventional commits and prepends generated notes to a CHANGELOG.md file, ensuring clear communication about project modifications. The process is triggered automatically on pushes to the main branch by a release workflow.

When to use it

  • To automatically generate changelogs for software projects following a defined commit message convention.
  • When you want to streamline the update process and provide users with a clear record of changes.
  • For teams using conventional commits and seeking an automated way to maintain a CHANGELOG.md file.
  • To easily view recent releases and their associated notes on GitHub.

Key capabilities

  • Automated Changelog Generation: Automatically creates changelog entries based on commit types.
  • Conventional Commits Support: Relies on conventional commits for determining changelog section headings.
  • Section Mapping: Maps specific commit types (feat, fix, perf, revert, and breaking changes) to corresponding sections in the changelog (Features, Bug Fixes, Performance Improvements, Reverts, BREAKING CHANGES).
  • GitHub Integration: Allows viewing of GitHub release notes and recent releases.

Example prompts

  • "Show me the current changelog."
  • "List the last 10 releases with their dates."
  • "What are the breaking changes in the latest version?"

Tips & gotchas

  • Conventional Commits Required: This skill relies on commit messages adhering to the conventional commits format. Consider using the conventional-commits skill for formatting guidance.
  • Main Branch Only: Changelog generation only occurs when commits are pushed to the main branch.
  • Commit Type Filtering: Commit types like chore, docs, refactor, test, and ci will not appear in the changelog.