checklist-release

Name: checklist-release
Availability: InStock
Author: akourmaz

Automate seven-phase go/no-go pre-release verification for software releases.

Updated Mar 2, 2026

Search Tags:#devops #checklist #deployment #verification #release #quality-assurance #go-no-go

Ready to run

npx skills add https://github.com/akourmaz/translate2 --skill checklist-release

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: checklist-release
Source: https://github.com/akourmaz/translate2/tree/main/.agents/skills/checklist-release
Command: npx skills add https://github.com/akourmaz/translate2 --skill checklist-release

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Pre-release verification tasks often miss critical checks leading to production issues. This skill provides a structured, repeatable process to ensure code quality, documentation, infrastructure, security, monitoring, deployment readiness, and post-deploy readiness.

Core Features & Use Cases

Seven-phase Go/No-Go release checklist covering code readiness, docs, infra, security, monitoring, deployment, and post-deploy validation.
Use cases include sprint-end releases, major/minor version launches, and service rollouts requiring formal go/no-go decision gates.

Quick Start

Follow this seven-phase checklist before every production release.

Frequently Asked Questions about checklist-release

High-intent search queries and answers about installing and using this skill.

FAQPage Schema

How do I automate pre-release verification for production deployments?▼

You can automate pre-release verification by applying a structured seven-phase go/no-go checklist that validates code, documentation, infrastructure, security, monitoring, and rollback readiness before production deployment.

What is a go/no-go release checklist and when do I need it?▼

A go/no-go release checklist is a formal decision gate validating software readiness across seven phases. It is needed during sprint-end releases, major or minor version launches, and post-change service rollouts to prevent production issues.

How do I ensure deployment readiness and rollback safety before a major version launch?▼

Deployment and rollback readiness are ensured by enforcing severity levels and checklists across seven phases, validating code quality, infrastructure, security, and post-deploy monitoring to confirm safe major version launches.

Does this pre-release checklist work for minor version updates and post-change rollouts?▼

Yes, the pre-release checklist applies to minor version updates and post-change rollouts, providing a repeatable verification process to validate code, security, and infrastructure readiness for any production deployment.

What is the best way to enforce quality assurance gates for DevOps release cycles?▼

The best way to enforce quality assurance gates is by applying a seven-phase go/no-go decision framework with severity levels and checklists that validate code, docs, infra, and monitoring during every DevOps release cycle.