Skip to content
TrustedSkillsbeta
Back to all skills

Release Checklist

Checked
zbruhnke·vlatest·devops·MIT

This "Release Checklist" skill automates deployment verification by generating a structured list of steps, ensuring consistent and reliable releases.

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 zbruhnke/claude-code-starter --skill release-checklist -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

zbruhnke

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 zbruhnke/claude-code-starter at 6b95b88bf2.

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

Scanned
1 file, 147 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 zbruhnke-release-checklist skill provides a structured checklist to guide software releases. It ensures critical steps are not missed, promoting consistency and reducing errors in deployment processes. This helps teams maintain quality and stability during release cycles.

When to use it

  • When preparing for a new software version launch.
  • To standardize the release process across different projects or teams.
  • As part of an automated CI/CD pipeline to ensure all pre-release steps are completed.
  • For onboarding new team members and providing them with a clear release procedure.

Key capabilities

  • Provides a comprehensive checklist for software releases.
  • Helps maintain consistency in deployment processes.
  • Reduces the risk of errors during releases.

Example prompts

  • "Generate a release checklist for version 1.2.0."
  • "Show me the steps required to prepare a release candidate."
  • "What are the pre-release tasks I need to complete?"

Tips & gotchas

The skill assumes a basic understanding of software development and deployment workflows. It's designed as a guide, so adapt it to your specific project needs and environment.