The release checklist - QA pass, reviews in, rollback written, backup tested, then merge, migrate, deploy and announce, each on the founder's go - and the watch after. Use for every release to users.
Installs into .claude/skills of the current project.
Are you the author of Release?
Add the live security badge to your README. It updates with every re-scan.
[](https://www.skillsdirectory.com/skills/fadi88-release)
---
name: release
description: "The release checklist - QA pass, reviews in, rollback written, backup tested, then merge, migrate, deploy and announce, each on the founder's go - and the watch after. Use for every release to users."
disable-model-invocation: true
---
<!-- Generated by tools/sync_adapters.py from skills/release/SKILL.md. Edit the source, not this file. -->
# Release
Run in order. Any line not met stops the release.
## Before
1. `docs/work/<id>/qa.md` says PASS or PASS WITH KNOWN ISSUES, and the founder has read the issues.
2. `security.md` has no open critical or high; `legal` has no RED on the launch path.
3. If the product has a free tier or trial, every cap row is `T`: a test proves each per-user,
per-device and global limit holds.
4. `python tools/run_all.py` green on the release commit; CI green on the same commit.
5. Release notes written in `docs/work/<id>/release.md`: what users will notice, in their words.
6. **Rollback written down:** the exact steps and how long they take. If a migration cannot be
reversed, say so and get the founder's explicit acceptance.
7. Backup taken and a restore of it tried, this session.
## Steps, each on its own go (`skills/ordered-steps/`)
1. Merge to main.
2. Run migrations.
3. Deploy.
4. Smoke test production: the main flow end to end, as a user.
5. Announce.
## After
Watch errors and the feature's success number for the window set in the spec. If either goes
wrong, roll back first and investigate second. Write a short entry in `docs/HISTORY.md`.
