Skip to content
TrustedSkillsbeta
Back to all skills

Release Standards

Checked
asiaostrich·vlatest·devops

Automates releasing code based on predefined standards, ensuring consistent and reliable deployments across environments for faster development cycles.

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-standards --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

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 helps automate the process of adhering to release standards. It can generate checklists based on predefined criteria, automatically update documentation with version numbers, and ensure consistent tagging across repositories. The goal is to streamline releases and reduce errors by enforcing established procedures.

When to use it

  • When preparing for a software release and needing to verify adherence to internal guidelines.
  • To automate the creation of release notes and changelogs based on commit history.
  • For ensuring consistent versioning across multiple repositories or projects.
  • During automated build processes to validate that releases meet defined quality gates.

Key capabilities

  • Checklist generation from predefined standards
  • Automated documentation updates with version numbers
  • Consistent tagging of repositories
  • Release note and changelog creation based on commit history

Example prompts

  • "Generate a release checklist for version 1.2.0."
  • "Update the README file to reflect the current version number."
  • "Create release notes from the commits between v1.1 and v1.2."

Tips & gotchas

This skill requires pre-configured release standards to be effective. Ensure these standards are clearly defined before using the skill for optimal results.