Skip to content
TrustedSkillsbeta
Back to all skills

Auto Release Manager

Checked
dev-gom·vlatest·devops·Apache-2.0

Automates deployment workflows by triggering releases based on defined criteria, streamlining DevOps and reducing manual intervention.

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 dev-gom/claude-code-marketplace --skill auto-release-manager --full-depth -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

dev-gom

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 dev-gom/claude-code-marketplace at eed6aa291a.

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

Commit
eed6aa291a
Manifest
plugins/auto-release-manager/skills/SKILL.md
Scanned
9 files, 1,629 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 auto-release-manager skill automates the software release process. It handles tasks like version bumping, tag creation, and deployment to various environments (e.g., staging, production). This reduces manual effort and potential errors associated with releasing new versions of your software.

When to use it

  • Automated deployments: When you want to automate the steps involved in deploying a new version of your application after code changes are merged.
  • Continuous Delivery (CD): To streamline your CD pipeline by automatically triggering releases based on specific events, like successful builds or pull request merges.
  • Release branching workflows: When managing multiple release branches and need to ensure consistent tagging and deployment across them.
  • Reducing manual errors: To minimize the risk of human error during the often complex software release process.

Key capabilities

  • Version bumping (semantic versioning)
  • Tag creation in Git repositories
  • Deployment to staging environments
  • Deployment to production environments

Example prompts

  • "Release version 1.2.3 to the staging environment."
  • "Create a release tag for commit hash abcdefg."
  • "Deploy the latest tagged version to production."

Tips & gotchas

The skill requires appropriate permissions within your Git repository and deployment environments. Ensure that the AI agent has access to perform these actions before use.