Skip to content
TrustedSkillsbeta
Back to all skills

Create Changeset

Checked
openameba·vlatest·other·MIT

Generates structured code changesets based on natural language instructions, facilitating efficient software development workflows.

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 openameba/spindle --skill create-changeset -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

openameba

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 openameba/spindle at 76b0bcdd71.

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

Scanned
1 file, 135 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

The create-changeset skill enables AI agents to generate changesets, which are essential for tracking and managing software modifications before deployment. It streamlines the workflow by automatically documenting what has changed in a codebase or project configuration.

When to use it

  • Preparing pull requests to ensure all modifications are clearly documented for reviewers.
  • Managing version control workflows that require explicit change logs before merging.
  • Automating release notes generation based on recent commits or file alterations.
  • Coordinating updates across multiple files where a single summary is needed.

Key capabilities

  • Generates standardized changeset files for version tracking.
  • Captures details of specific codebase modifications.
  • Facilitates structured communication of project updates.

Example prompts

  • "Create a changeset for the recent updates to the authentication module and database schema."
  • "Generate a changeset summarizing all frontend component refactors completed today."
  • "Draft a changeset entry detailing the new API endpoints added in this commit."

Tips & gotchas

Ensure your repository is configured with the necessary hooks or scripts to recognize generated changesets, as they often require specific formatting to be processed by CI/CD pipelines. Always review the generated content before finalizing it to ensure accuracy regarding the scope of changes.