Skip to content
TrustedSkillsbeta
Back to all skills

Create Release Tags

Checked
re2zero·vlatest·devops·MIT

Automatically generates semantic release tags (e.g., v1.2.3) based on commit messages for streamlined 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 re2zero/deepin-skills --skill create-release-tags -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

re2zero

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 re2zero/deepin-skills at 0095fec1c6.

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

Commit
0095fec1c6
Manifest
create-release-tags/SKILL.md
Scanned
1 file, 225 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

This skill automates the creation of release tags based on semantic versioning. It can generate tags like v1.2.3, incrementing patch versions, or creating new minor/major releases as needed. The skill aims to streamline and standardize the tagging process in software development workflows.

When to use it

  • After a successful build and testing cycle, you need to automatically create a release tag for your project.
  • When bumping the patch version of an existing release (e.g., fixing a bug).
  • To generate a new minor or major release tag based on commit history or other criteria.
  • For consistent tagging across multiple repositories and projects.

Key capabilities

  • Generates semantic version tags (vX.Y.Z)
  • Supports incrementing patch, minor, and major versions
  • Automated tag creation based on defined rules

Example prompts

  • "Create a new release tag for the current build."
  • "Bump the patch version of v1.2.0."
  • "Generate a new minor release tag."

Tips & gotchas

The skill requires access to repository information and permissions to create tags. Ensure proper configuration and authentication are in place before use.