Skip to content
TrustedSkillsbeta
Back to all skills

Release Guard

Checked
d-o-hub·vlatest·devops·MIT

Release Guard automatically rolls back deployments if predefined thresholds are breached, ensuring stable releases and minimizing downtime.

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 d-o-hub/rust-self-learning-memory --skill release-guard -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

d-o-hub

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 d-o-hub/rust-self-learning-memory at da7210f59b.

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

Commit
da7210f59b
Manifest
.agents/skills/release-guard/SKILL.md
Scanned
3 files, 235 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 release-guard skill provides automated release management capabilities, specifically focused on ensuring code quality and preventing regressions. It can automatically run tests and checks before allowing a release to proceed, significantly reducing the risk of deploying faulty software. This helps streamline deployments and improve overall software reliability.

When to use it

  • Automated Release Pipelines: Integrate with CI/CD systems to gate releases based on test results.
  • Pre-Production Checks: Run comprehensive tests before promoting code to staging or production environments.
  • Regression Prevention: Automatically verify that new changes haven't introduced regressions in existing functionality.
  • Release Branch Management: Ensure release branches remain stable and free of errors prior to final deployment.

Key capabilities

  • Automated test execution
  • Release gating based on test results
  • Integration with CI/CD pipelines
  • Regression testing

Example prompts

  • "Run the integration tests before allowing this release."
  • "Check for any regressions in the payment processing module."
  • "Ensure all unit tests pass before promoting to staging."

Tips & gotchas

The skill requires proper configuration within your CI/CD environment. It's crucial to define clear test criteria and thresholds for successful releases.