Receber por email
← Voltar para o catálogo

release-check

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

3.1kestrelas
Atualizado há 4 meses

Ver no GitHub ↗ Licença: MIT

Como adicionar

/plugin marketplace add davepoon/buildwithclaude

O comando exato pode variar conforme o repositório. Confira o README no GitHub.

Para o autor da skill

Cole no README do seu repo

Mostra que sua skill está catalogada na Skillteca, gera backlink e tráfego rastreável.

[![Skillteca](https://www.skillteca.com.br/api/badge/release-check/svg)](https://www.skillteca.com.br/skills/release-check)

Skills relacionadas

Ver todas de Desenvolvimento →

Alerta por categoria

Receba novas skills de Desenvolvimento toda segunda

1 email curto, só com as skills novas de Desenvolvimento. 4 minutos de leitura, sem spam, cancela com 1 clique.

Você confirma o email no primeiro envio. Sem spam. Cancela com 1 clique.

Ler descrição completa

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

  1. Runs the SIGN IN checklist
  2. TIME OUT 1 — Documentation and Debt Check: verifies CHANGELOG, TECH_DEBT, specs, and docs
  3. TIME OUT 2 — Testing and Quality Gate: runs all tests, code health scan, quality verification
  4. TIME OUT 3 — Security and Release Gate: runs security audit, security verification, release readiness
  5. Writes release assessment to docs/reviews/release-check-{version}.md
  6. 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
Compartilhar X LinkedIn