Skip to content
TrustedSkillsbeta
Back to all skills

Release Prep

Checked
cartridge-gg·vlatest·devops

Streamlines release preparation by automating environment setup and dependency checks, saving developers time & reducing errors during deployments.

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 cartridge-gg/controller --skill release-prep -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

cartridge-gg

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 cartridge-gg/controller at b282b7b18d.

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

Commit
b282b7b18d
Manifest
.agents/skills/release-prep/SKILL.md
Scanned
1 file, 40 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 cartridge-gg-release-prep skill automates preparation steps necessary before a software release. It handles tasks like version bumping, changelog generation, and creation of release notes, streamlining the release process. This ensures consistency and reduces errors in deployments by automating repetitive actions.

When to use it

  • Preparing for a new major or minor software release.
  • Automating the creation of release documentation (changelogs, release notes).
  • Ensuring consistent versioning across repositories and packages.
  • Reducing manual effort and potential errors in pre-release tasks.

Key capabilities

  • Version bumping
  • Changelog generation
  • Release note creation

Example prompts

  • "Prepare the next release for project X, using semantic versioning."
  • "Generate a changelog based on recent commits for version 1.2.3."
  • "Create release notes summarizing changes in version 2.0."

Tips & gotchas

The skill requires access to relevant repositories and configuration files to perform its tasks effectively. Ensure proper permissions are granted before use, as incorrect configurations can lead to unexpected results or errors during the preparation process.