Skip to content
TrustedSkillsbeta
Back to all skills

Git Release

Checked
krissss·vlatest·backend

Automates Git tag creation, release branch management, and deployment to specified environments based on defined workflows.

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 krissss/skills --skill git-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

krissss

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 krissss/skills at 0a7583936d.

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

Commit
0a7583936d
Manifest
skills/git-release/SKILL.md
Scanned
1 file, 223 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 Git release workflows, handling tagging, branch management, and potentially deployment based on configured triggers. It simplifies the process of creating releases from your codebase, ensuring consistency and reducing manual errors. The tool supports both semantic versioning and custom tag formats for release identification.

When to use it

  • You need to automate the creation of Git tags and releases after merging code into a main branch.
  • You want to streamline the process of deploying software based on new Git tags or branches.
  • Your team follows semantic versioning (SemVer) and requires automated tag generation.
  • You're looking for a way to manage release branches and their eventual merging back into your primary codebase.

Key capabilities

  • Automated Git tagging
  • Branch management
  • Semantic Versioning support
  • Custom tag format support
  • Deployment triggers (potential)

Example prompts

  • "Create a new release for version 1.2.3."
  • "Tag the current commit as 'release-candidate-1'."
  • "Release this branch to production after merging into main."

Tips & gotchas

  • Requires access and permissions to your Git repository.
  • Deployment triggers require careful configuration to avoid unintended deployments.