Skip to content
TrustedSkillsbeta
Back to all skills

Release

Checked
asiaostrich·vlatest·devops

This "Release" skill automates deployment pipelines, streamlining software releases and reducing manual errors for faster delivery.

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 asiaostrich/universal-dev-standards --skill release -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

asiaostrich

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 asiaostrich/universal-dev-standards at 2c7106b0d4.

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

Commit
2c7106b0d4
Manifest
skills/release-standards/SKILL.md
Scanned
15 files, 3,277 lines
Copies in repo
3 — 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 software releases, handling tasks like version bumping, tag creation, and deployment to various environments. It ensures a consistent and repeatable release process, reducing errors and improving efficiency. The skill supports multiple repository types and integrates with common CI/CD pipelines.

When to use it

  • Automating the release of new versions of your software.
  • Deploying applications to staging or production environments after testing.
  • Creating release branches and managing tags in Git repositories.
  • Standardizing the release process across multiple projects.

Key capabilities

  • Version bumping (semantic versioning)
  • Git tag creation
  • Deployment to various environments
  • Support for multiple repository types
  • CI/CD pipeline integration

Example prompts

  • "Release version 1.2.3 to the production environment."
  • "Create a release branch for feature X and bump the patch version."
  • "Deploy the latest tagged commit to staging."

Tips & gotchas

The skill requires appropriate permissions within your Git repository and deployment environments. Ensure that necessary credentials are configured before use, as incorrect configuration can lead to failed releases or unauthorized access.