Release Check

davepoon/release-check

Pre-release verification checklist. Validates features, tests, docs, security, and quality gates before shipping. Delegates to the Centinela (QA) agent.

396 tokens

context cost

the whole folder, loaded on every use

files

instructions only

copies elsewhere

how many repositories repackaged it

3248

stars on the repo

on the repository, not the skill itself

Install

one command, takes just this skill from the repository

npx skills add https://github.com/davepoon/buildwithclaude --skill release-check

The instruction itself

7 sections, as written by the author

Release Check

Runs pre-release verification using the Centinela (QA) agent. This is the highest-stakes checklist in the system.

When to Use This Skill

Before any release to production
Before tagging a version
As a final quality gate after all features are implemented and reviewed

What This Skill Does

Runs the SIGN IN checklist
TIME OUT 1 — Documentation and Debt Check: verifies CHANGELOG, TECH_DEBT, specs, and docs
TIME OUT 2 — Testing and Quality Gate: runs all tests, code health scan, quality verification
TIME OUT 3 — Security and Release Gate: runs security audit, security verification, release readiness
Writes release assessment to docs/reviews/release-check-{version}.md
Issues final verdict: READY FOR RELEASE or BLOCKED (with specific reasons)

How to Use

Basic Usage

/release-check v1.2.0

Example

User: /release-check v2.0.0

Output: A release assessment at docs/reviews/release-check-v2.0.0.md with:

Documentation completeness check
Test results and quality gate status
Security audit summary
Final verdict with specific blocking reasons if any

Tips

This is the last line of defense before code reaches users
A blocked release here prevents issues from reaching production
Three TIME OUT checkpoints cover docs, quality, and security independently

How to use it

Copy the folder

Take davepoon/release-check from the repository into ~/.claude/skills for personal use, or into .claude/skills inside a project.

Check the name does not clash

The agent identifies a skill by the name field in its header. Two skills with the same name cannot sit side by side — one of them will be ignored.