How do I install the Deploy Checklist skill?

Run npx skillmds@latest add nota-america/deploy-checklist in your terminal (requires Node.js), paste this page's agent-chat prompt into Claude, Cursor, or any MCP-connected agent, or download the SKILL.md file and copy it into your agent's skills directory.

Is Deploy Checklist safe to use?

This skill has not completed SkillMD's automated safety review yet. SkillMD never runs a skill's scripts for you; review the SKILL.md before installing.

Which AI agents work with Deploy Checklist?

This skill is tagged as working with Claude Code, Claude.ai, OpenAI Codex. SKILL.md is an open format, so most agents that read a skills directory can load it too.

Is Deploy Checklist free to use?

Yes. Installing skills from SkillMD is free, and the skill stays under its author's original license.

Who published Deploy Checklist?

nota-america (@nota-america) published this skill. Their other Agent Skills are listed on their SkillMD profile.

Deploy Checklist by nota-america — Agent Skill

Name: Deploy Checklist
Author: nota-america

Deploy Checklist

Pre-deployment verification checklist. Use when about to ship a release, deploying a change with database migrations or feature flags, verifying CI status and approvals before going to production, or documenting rollback triggers ahead of time.

nota-america 44c5654 2.3 KB Updated Sep 17, 2026

File contents

/deploy-checklist

If you see unfamiliar placeholders or need to check which tools are connected, see CONNECTORS.md ({{ref:connectors}}).

Generate a pre-deployment checklist to verify readiness before shipping.

Usage

/deploy-checklist $ARGUMENTS

Output

## Deploy Checklist: [Service/Release]
**Date:** [Date] | **Deployer:** [Name]

### Pre-Deploy
- [ ] All tests passing in CI
- [ ] Code reviewed and approved
- [ ] No known critical bugs in release
- [ ] Database migrations tested (if applicable)
- [ ] Feature flags configured (if applicable)
- [ ] Rollback plan documented
- [ ] On-call team notified

### Deploy
- [ ] Deploy to staging and verify
- [ ] Run smoke tests
- [ ] Deploy to production (canary if available)
- [ ] Monitor error rates and latency for 15 min
- [ ] Verify key user flows

### Post-Deploy
- [ ] Confirm metrics are nominal
- [ ] Update release notes / changelog
- [ ] Notify stakeholders
- [ ] Close related tickets

### Rollback Triggers
- Error rate exceeds [X]%
- P50 latency exceeds [X]ms
- [Critical user flow] fails

Customization

Tell me about your deploy and I'll customize the checklist:

"We use feature flags" → adds flag verification steps
"This includes a database migration" → adds migration-specific checks
"This is a breaking API change" → adds consumer notification steps

If Connectors Available

If ~~source control is connected:

Pull the release diff and list of changes
Verify all PRs are approved and merged

If ~~CI/CD is connected:

Check build and test status automatically
Verify pipeline is green before deploy

If ~~monitoring is connected:

Pre-fill rollback trigger thresholds from current baselines
Set up post-deploy metric watch

Tips

Run before every deploy — Even routine ones. Checklists prevent "I forgot to..."
Customize once, reuse — Tell me your stack and I'll remember your deploy process.
Include rollback criteria — Decide when to roll back before you deploy, not during.

---name: deploy-checklistdescription: Pre-deployment verification checklist. Use when about to ship a release, deploying a change with database migrations or feature flags, verifying CI status and approvals before going to production, or documenting rollback triggers ahead of time.---# /deploy-checklist> If you see unfamiliar placeholders or need to check which tools are connected, see CONNECTORS.md (`{{ref:connectors}}`).Generate a pre-deployment checklist to verify readiness before shipping.## Usage```/deploy-checklist $ARGUMENTS```## Output```markdown## Deploy Checklist: [Service/Release]**Date:** [Date] | **Deployer:** [Name]### Pre-Deploy- [ ] All tests passing in CI- [ ] Code reviewed and approved- [ ] No known critical bugs in release- [ ] Database migrations tested (if applicable)- [ ] Feature flags configured (if applicable)- [ ] Rollback plan documented- [ ] On-call team notified### Deploy- [ ] Deploy to staging and verify- [ ] Run smoke tests- [ ] Deploy to production (canary if available)- [ ] Monitor error rates and latency for 15 min- [ ] Verify key user flows### Post-Deploy- [ ] Confirm metrics are nominal- [ ] Update release notes / changelog- [ ] Notify stakeholders- [ ] Close related tickets### Rollback Triggers- Error rate exceeds [X]%- P50 latency exceeds [X]ms- [Critical user flow] fails```## CustomizationTell me about your deploy and I'll customize the checklist:- "We use feature flags" → adds flag verification steps- "This includes a database migration" → adds migration-specific checks- "This is a breaking API change" → adds consumer notification steps## If Connectors AvailableIf **~~source control** is connected:- Pull the release diff and list of changes- Verify all PRs are approved and mergedIf **~~CI/CD** is connected:- Check build and test status automatically- Verify pipeline is green before deployIf **~~monitoring** is connected:- Pre-fill rollback trigger thresholds from current baselines- Set up post-deploy metric watch## Tips1. **Run before every deploy** — Even routine ones. Checklists prevent "I forgot to..."2. **Customize once, reuse** — Tell me your stack and I'll remember your deploy process.3. **Include rollback criteria** — Decide when to roll back before you deploy, not during.

Frequently asked questions