Skip to content
TrustedSkillsbeta
Back to all skills

Sentry Release Management

Checked
thebushidocollective·vlatest·devops

Automates release approvals, deployments, and rollbacks based on pre-defined rules and real-time monitoring data.

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 thebushidocollective/han --skill sentry-release-management -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

thebushidocollective

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 thebushidocollective/han at 19caa51d5f.

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

Commit
19caa51d5f
Manifest
plugins/specialized/sentry/skills/release-management/SKILL.md
Scanned
1 file, 182 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 release management tasks within Sentry, a popular error tracking and performance monitoring platform. It allows you to programmatically create, update, and close releases, streamlining your development workflow and improving visibility into application deployments. The skill supports specifying release versions, environments, and statuses directly through AI agent interaction.

When to use it

  • Automated Release Creation: Automatically create a new Sentry release whenever a deployment is triggered in your CI/CD pipeline.
  • Release Status Updates: Update the status of a Sentry release (e.g., "in progress," "failed") based on build or testing outcomes.
  • Closing Releases: Close releases after a period of stability, archiving associated error data and simplifying reporting.
  • Version Management: Ensure consistent versioning across your applications by automatically setting the release version number.

Key capabilities

  • Create Sentry releases
  • Update release statuses (e.g., in progress, failed)
  • Close Sentry releases
  • Specify release versions
  • Define environments for releases

Example prompts

  • "Create a new Sentry release for version 1.2.3 in the production environment."
  • "Mark the release 'my-app-v1' as failed."
  • "Close the release with version number 2024.01.15."

Tips & gotchas

  • Requires appropriate API keys and permissions configured within your Sentry account for authentication.
  • Ensure that the specified release versions align with your application’s versioning scheme to avoid confusion.