Use when (1) release is deployed and verified, (2) closing related issues and PRs, (3) creating GitHub release with changelog, (4) finalizing release documentation. Completes the release lifecycle.
Instalar com Codex ou Claude Copie este prompt, cole no Codex, Claude ou outro assistente e deixe que ele revise a página da skill e instale para você.
Um comando direto ignora o prompt de revisão. Verifique a origem antes de executá-lo.
Instruções da origem · Visualização somente leitura
name
gmacko-release-close
description
Use when (1) release is deployed and verified, (2) closing related issues and PRs, (3) creating GitHub release with changelog, (4) finalizing release documentation. Completes the release lifecycle.
## Deployment Verification### Web (Vercel)- [ ] Production URL accessible: https://app.example.com
- [ ] Smoke tests passed
- [ ] No error spikes in Sentry
### Mobile (if applicable)- [ ] iOS build submitted/approved
- [ ] Android build submitted/approved
- [ ] OTA update published (if applicable)
Ask user:
Before closing the release, please confirm:
Web production is stable? (yes/no)
Mobile apps are approved/live? (yes/no/not-applicable)
Any issues reported since deployment? (yes/no)
Step 2: Close Issues
Find and close related issues:
# List issues that should be closed
gh issue list --state open --label "status:in-progress"# Get issues linked to merged PRs
gh pr list --state merged --json number,title,closingIssuesReferences
Close each issue with comment:
# Close issue with release reference
gh issue close [number] --comment "Released in v[X.Y.Z].
Deployment verified on [date].
- Web: https://app.example.com
- Mobile: v[X.Y.Z] on App Store/Play Store"
# List merged branches
git branch --merged main | grep -v "main\|staging\|dev"# Delete local merged branches
git branch --merged main | grep -v "main\|staging\|dev" | xargs git branch -d
# Delete remote merged branches (with confirmation)# gh api repos/gmacko/project/branches --jq '.[].name' | ...
Ask user before deleting:
The following branches are merged and can be deleted:
feature/dark-mode
fix/login-bug
Delete these branches? (yes/no/selective)
Step 7: Notify Stakeholders
Prepare notification:
## Release Notification**Subject**: v[X.Y.Z] Released
**Body**:
Hi team,
We've just released v[X.Y.Z] to production!
### Highlights- [Key feature 1]
- [Key feature 2]
- [Important fix]
### Links- Production: https://app.example.com
- Release Notes: [GitHub Release URL]
- Mobile: Available on App Store / Play Store
### Metrics to Watch- Error rate in Sentry
- Performance in Vercel Analytics
- User feedback
Let me know if you notice any issues!
[Your name]
Suggest notification channels:
Slack #releases channel
Email to stakeholders
Update status page
Step 8: Archive Documentation
Finalize release documentation:
# Update docs/ai/releases/[date]-v[version].md## Final Status-**Released**: [timestamp]
-**GitHub Release**: [URL]
-**Git Tag**: v[X.Y.Z]
## Deployment Summary
| Platform | Status | URL/Version |
|----------|--------|-------------|
| Web | Live | https://app.example.com |
| iOS | Live | v[X.Y.Z] on App Store |
| Android | Live | v[X.Y.Z] on Play Store |
## Issues Closed
[List of closed issues]
## PRs Included
[List of merged PRs]
## Post-Release Observations### First 24 Hours- Error rate: [Normal/Elevated]
- Performance: [Normal/Degraded]
- User feedback: [Summary]
### Issues Discovered- [Any post-release issues and how they were handled]
---
**Release Closed By**: AI Assistant
**Closed At**: [timestamp]
