Skill Tracer
Skills › Knowledge Work Plugins › deploy-checklist

deploy-checklist

skill · 78 lines · Apache-2.0 · engineering/skills/deploy-checklist/SKILL.md

The facts

Its description

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.

The description the agent reads to decide when to use it.

From its settingsline 3

When it starts

The agent would pick this skill when the person is getting ready to ship a release or push a change to production and wants a readiness check — especially when the deploy involves database migrations, feature flags, or a need to agree on rollback triggers beforehand. It is triggered by the act of preparing to deploy, not by any other skill.

Things a person might say (the model's guesses)

  • “We're shipping the payments service v2.3 tonight, can you put together a deploy checklist?”
  • “I'm about to push a change with a database migration and a feature flag — what should I verify first?”
  • “Help me document rollback triggers before we go to production.”

A model's summary of when it is used.

A model's reading

What it takes when started

[service or release name]

What to type after its name when you start it.

From its settingsline 4

Licence

Apache-2.0, from LICENSE

The terms its author shares it under, which let it be shown here.

From the repositorylicence text

The text

Open on GitHub

Most marks come from matching words in the file, so treat them as pointers.

1---
2name: deploy-checklist
3description: 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.
4argument-hint: "[service or release name]"
5---
6
7# /deploy-checklist
8
9> If you see unfamiliar placeholders or need to check which tools are connected, see [CONNECTORS.md](../../CONNECTORS.md).
11Generate a pre-deployment checklist to verify readiness before shipping.

/deploy-checklist

If you see unfamiliar placeholders or need to check which tools are connected, see CONNECTORS.md.

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

Raw lines 1 to 12
Boilerplate, lines 13 to 18. The same text appears in 24 other files here. Close
13## Usage
15```
16/deploy-checklist $ARGUMENTS
17```
19## Output
21```markdown
22## Deploy Checklist: [Service/Release]
23**Date:** [Date] | **Deployer:** [Name]
25### Pre-Deploy
26- [ ] All tests passing in CI
27- [ ] Code reviewed and approved
28- [ ] No known critical bugs in release
29- [ ] Database migrations tested (if applicable)
30- [ ] Feature flags configured (if applicable)
31- [ ] Rollback plan documented
32- [ ] On-call team notified
34### Deploy
35- [ ] Deploy to staging and verify
36- [ ] Run smoke tests
37- [ ] Deploy to production (canary if available)
38- [ ] Monitor error rates and latency for 15 min
39- [ ] Verify key user flows
41### Post-Deploy
42- [ ] Confirm metrics are nominal
43- [ ] Update release notes / changelog
44- [ ] Notify stakeholders
45- [ ] Close related tickets
47### Rollback Triggers
48- Error rate exceeds [X]%
49- P50 latency exceeds [X]ms
50- [Critical user flow] fails
51```

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
Raw lines 19 to 52
53## Customization
55Tell me about your deploy and I'll customize the checklist:
56- "We use feature flags" → adds flag verification steps
57- "This includes a database migration" → adds migration-specific checks
58- "This is a breaking API change" → adds consumer notification steps

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
Raw lines 53 to 59
60## If Connectors Available
62If **~~source control** is connected:
63- Pull the release diff and list of changes
64- Verify all PRs are approved and merged
66If **~~CI/CD** is connected:
67- Check build and test status automatically
68- Verify pipeline is green before deploy
70If **~~monitoring** is connected:
71- Pre-fill rollback trigger thresholds from current baselines
72- Set up post-deploy metric watch

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
Raw lines 60 to 73
Uses an outside tool ~~source :62
Uses an outside tool ~~monitoring :70
74## Tips
761. **Run before every deploy** — Even routine ones. Checklists prevent "I forgot to..."
772. **Customize once, reuse** — Tell me your stack and I'll remember your deploy process.
783. **Include rollback criteria** — Decide when to roll back before you deploy, not during.

Tips

  1. 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.
Raw lines 74 to 78

From anthropics/knowledge-work-plugins at 2574e29, 2026-10-27. Skills read by DeepSeek V4.1 Flash on 2026-11-04. Summary and techniques by Claude Opus 5.5 on 2026-11-06.