Skip to content
TrustedSkillsbeta
Back to all skills

Api Changelog Versioning

Checked
aj-geddes·vlatest·writing·MIT

Provides API guidance and assistance for writing, documentation, and content creation.

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 aj-geddes/useful-ai-prompts --skill api-changelog-versioning -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

aj-geddes

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 aj-geddes/useful-ai-prompts at 3f5182cfd7.

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

Commit
3f5182cfd7
Manifest
skills/api-changelog-versioning/SKILL.md
Scanned
8 files, 588 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

api-changelog-versioning

What it does

This skill instructs AI agents to automatically generate structured changelog entries whenever an API version is updated. It ensures that release notes clearly document new features, deprecated endpoints, and breaking changes for developers.

When to use it

  • You need to maintain a consistent history of API modifications across multiple releases.
  • Your team requires clear documentation of breaking changes before deploying updates.
  • You want to automate the creation of CHANGELOG.md or similar release notes files.
  • You are managing public APIs where users rely on version-specific stability guarantees.

Key capabilities

  • Generates timestamped entries for specific API versions.
  • Categorizes changes into features, bug fixes, and deprecations.
  • Highlights breaking changes that require user action.
  • Formats output in standard markdown or JSON structures.

Example prompts

  • "Generate a changelog entry for API version 2.1, adding the new /users endpoint and deprecating /v1/auth."
  • "Create a release note summary for the latest update, focusing on breaking changes that affect existing integrations."
  • "Draft a structured changelog for this week's API updates, including performance improvements and security patches."

Tips & gotchas

Ensure your AI agent has access to the specific details of the changes made in the current release cycle. Without accurate input about what was modified, the generated changelog may lack critical information or miss breaking changes entirely.