home / skills / amnadtaowsoam / cerebraskills / release-checklist-gate
This skill guides you through release readiness by validating code quality, documentation, testing, and approvals before production deployment.
npx playbooks add skill amnadtaowsoam/cerebraskills --skill release-checklist-gateReview the files below or copy the command above to add this skill to your agents.
---
name: Release Checklist Gate
description: Checklist gate for production release covering testing, documentation, rollback plan, and stakeholder sign-off
---
# Release Checklist Gate
## Overview
Checklist gate for production release - must pass all items before deploying to production
## Why This Matters
- **Safety**: Don't miss important steps
- **Quality**: Release has standards
- **Accountability**: Know who approved
- **Rollback ready**: Ready to rollback if problems occur
---
## Release Checklist
```markdown
## Pre-Release Checklist
### Code Quality
☐ All tests passing (unit, integration, E2E)
☐ Code review approved
☐ No critical/high security issues
☐ Performance benchmarks pass
☐ No known bugs (P0/P1)
### Documentation
☐ Changelog updated
☐ Release notes written
☐ API docs updated (if applicable)
☐ Migration guide (if breaking changes)
☐ Runbook updated
### Testing
☐ Smoke tests pass in staging
☐ Load testing completed (if needed)
☐ Security testing completed
☐ UAT completed (if applicable)
☐ Rollback tested
### Infrastructure
☐ Database migrations tested
☐ Feature flags configured
☐ Monitoring/alerts in place
☐ Rollback plan documented
☐ Capacity planning done
### Communication
☐ Stakeholders notified
☐ Support team briefed
☐ Customers notified (if needed)
☐ Status page prepared
### Approvals
☐ Tech lead approval
☐ Product owner approval
☐ Security team approval (if needed)
☐ Change management approval
### Deployment
☐ Deployment window scheduled
☐ On-call engineer assigned
☐ Deployment runbook ready
☐ Rollback command ready
```
---
## Automated Checks
```yaml
# .github/workflows/release-gate.yml
name: Release Gate
on:
push:
tags:
- 'v*'
jobs:
release-gate:
runs-on: ubuntu-latest
steps:
- name: Check Tests
run: npm test
- name: Check Security
run: npm audit --audit-level=high
- name: Check Changelog
run: |
if ! grep -q "${{ github.ref_name }}" CHANGELOG.md; then
echo "Changelog not updated"
exit 1
fi
- name: Check Approvals
uses: actions/github-script@v6
with:
script: |
const approvals = await github.rest.pulls.listReviews({
owner: context.repo.owner,
repo: context.repo.repo,
pull_number: context.issue.number
});
if (approvals.data.length < 2) {
throw new Error('Need 2 approvals');
}
```
---
## Release Template
```markdown
## Release v1.2.3
### Summary
[Brief description of release]
### Changes
- Feature: Added user authentication
- Bug fix: Fixed login timeout
- Performance: Improved API response time
### Breaking Changes
- None
### Migration Steps
1. Run database migration: `npm run migrate`
2. Update environment variables
3. Restart services
### Rollback Plan
```bash
# Rollback to v1.2.2
kubectl set image deployment/api api=myapp:v1.2.2
npm run migrate:rollback
```
### Testing
- ✓ All tests pass
- ✓ Smoke tests pass in staging
- ✓ Load testing completed
### Approvals
- ✓ Tech Lead: @john
- ✓ Product Owner: @jane
- ✓ Security: @bob
### Deployment
- Date: 2024-01-16
- Time: 10:00 AM UTC
- On-call: @alice
```
---
## Summary
**Release Checklist Gate:** Must pass all items before release
**Categories:**
- Code quality (tests, review, security)
- Documentation (changelog, notes, runbook)
- Testing (smoke, load, UAT)
- Infrastructure (migrations, monitoring)
- Communication (stakeholders, support)
- Approvals (tech lead, product, security)
**Enforcement:**
- Automated checks (CI)
- Manual checklist (release template)
- Required approvals (2+ reviewers)
**No release without complete checklist**
This skill enforces a production release checklist gate that must pass all items before deploying. It combines automated CI checks with a manual release template to ensure testing, documentation, rollback readiness, and stakeholder sign-off. It prevents releases that lack approvals or essential artifacts.
The skill runs CI checks on tagged releases to verify tests, security audits, and changelog updates. It pairs those automated gates with a human checklist and a release template that captures runbooks, rollback commands, approvals, and communication steps. If any required check or approval is missing, the gate blocks the deployment until resolved.
What happens if an automated check fails?
The gate fails and blocks the release; resolve the failing check (fix tests, security issues, or update changelog) and re-run the release process.
How many approvals are required?
The default is at least two approvals for releases; require additional approvals from security or change management when applicable.
Is a rollback plan mandatory?
Yes. A documented and tested rollback plan is required before production deployment to ensure safe recovery from incidents.