Skip to content
TrustedSkillsbeta
Back to all skills

Release Check

Checked
drillan·vlatest·devops·MIT

This "Release Check" verifies deployment readiness by validating configurations and dependencies, ensuring smoother releases and reducing errors.

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 drillan/speckit-gates --skill release-check -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

drillan

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 drillan/speckit-gates at 1409cad701.

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

Commit
1409cad701
Manifest
skills/release-check/SKILL.md
Scanned
4 files, 1,324 lines
Copies in repo
2 — all of them scanned
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 Check skill validates a project's readiness for release by examining key configurations and dependencies. It assesses the completeness of specification documents, documentation files, version numbers, and API documentation against defined requirements. The skill produces a ReleaseChecklist report detailing the status of each check, helping to identify and address potential issues before deployment.

When to use it

  • Before initiating a new release cycle.
  • To ensure all required artifacts (specifications, plans, tasks) are complete.
  • To verify consistency in version numbers across different files.
  • When API documentation needs to be validated against contract specifications.

Key capabilities

  • Artifact Validation: Checks for the existence and completeness of spec.md, plan.md, and tasks.md files, as well as task completion status.
  • Documentation Verification: Validates the presence and content of README.md (including a usage section) and CHANGELOG.md (including an unreleased section).
  • Version Consistency: Compares version numbers in package.json and CHANGELOG.md, ensuring they match if both are present.
  • API Documentation Checks: Verifies the existence of API documentation and endpoint coverage when contracts exist.
  • Release Checklist Output: Generates a structured report (ReleaseChecklist) indicating overall readiness status (Ready/Not Ready) with detailed pass/fail statuses for each check.

Example prompts

  • "Check if we're ready for release."
  • "Run the release checklist and show me any issues."
  • "Validate the release artifacts."

Tips & gotchas

  • This is a manual skill, intended to be run before creating a release.
  • The skill relies on specific file names (spec.md, plan.md, etc.). Ensure these files exist and are named correctly in your project.
  • Version checks are optional; they only occur if both package.json and CHANGELOG.md contain version numbers.