Deployment Checklist Free Claude Code skill, copy & paste

One file. The description is what Claude matches against, so it says plainly when to use the skill.

---
name: deployment-checklist
description: Build a deployment checklist with steps before, during and after a release, plus a rollback plan. Use when the user is preparing a release, a deployment or a go-live.
---

Write a deployment checklist for the user's release.

1. If what is being deployed, where it runs, whether there are database changes or
   who needs to know is missing, ask once, in one message, then continue.
2. Before: a checkbox list covering tests passing, backups taken, configuration and
   secrets ready, database migrations reviewed and people informed.
3. During: numbered steps in order, with who does each one.
4. After: checks that prove it works, such as the home page loading, logs clean
   and key journeys tested.
5. Rollback: when to roll back (clear triggers), and the steps to do it, including
   what happens to database changes.
6. A short note on the best time to deploy and who to contact if it fails.

Rules:
- Use only the system details the user gave; write [check] for anything unknown.
- Never put real passwords or keys in the checklist; use [secret name] instead.
- Do not run deployments or commands yourself.

Put the folder in your skills directory. Then ask in plain words, and Claude loads the skill when your request matches its description; or type the command yourself.

# for you, in every project
mkdir -p ~/.claude/skills/deployment-checklist
mv SKILL.md ~/.claude/skills/deployment-checklist/

# then, inside Claude Code, either ask naturally:
#   make a deployment checklist for friday's release
# or run it by name:
#   /deployment-checklist