AutoGineer
Generated banner for Deploy Checklist
Generated logo for Deploy Checklist

Deploy Checklist

AnthropicOfficialPublished by Anthropic

  • Skill
  • Content generator
  • Cloud and DevOps
  • Apache-2.0
  • No issues found
Download ZIP

From the author

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 by Anthropic

AutoGineer summary

Written by AutoGineer from the skill’s own files, not by the author

The deploy-checklist skill provides a standardized, customizable framework for verifying software releases before they reach production. It helps teams systematically track critical deployment steps, from CI status and code approvals to database migrations and rollback planning. By generating a tailored checklist, it reduces the risk of human error during high-stakes release cycles.

What it does

  • Generates a structured checklist for pre-deployment, deployment, and post-deployment phases.
  • Allows customization based on specific deployment needs like feature flags or database migrations.
  • Provides a template for defining clear rollback triggers and thresholds.
  • Integrates with connected tools to pull release diffs, verify CI status, and pre-fill monitoring baselines.
  • Encourages consistent documentation of release notes and stakeholder notifications.

When to use it

  • Before shipping a new software release or production update.
  • When deploying changes involving database migrations or feature flag toggles.
  • To ensure all CI/CD pipeline requirements and code approvals are met.
  • When establishing clear rollback criteria prior to initiating a deployment.

Advantages

  • Reduces the likelihood of oversight during complex deployment procedures.
  • Standardizes the release process across different services and teams.
  • Promotes proactive risk management by requiring documented rollback triggers.
  • Adapts to specific technical requirements like breaking API changes or canary deployments.

Usage examples

“/deploy-checklist UserAuthService”
Generates a standard pre-deployment checklist template for the UserAuthService release.
“/deploy-checklist BackendAPI, this includes a database migration”
Generates a customized checklist for the BackendAPI that includes specific verification steps for database migration success.

Install

  1. Download the skill as a ZIP:

    https://mp-staging.autogineer.com/agent-skills/anthropics/deploy-checklist/download

  2. Unzip it into the cross-client skills folder of your project:

    mkdir -p .agents/skills && unzip deploy-checklist.zip -d .agents/skills

Documentation by Anthropic

/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.

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

  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.

Files

SKILL.md

/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.

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

  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.

Requirements and compatibility

Written for: Claude Code, Claude apps

Works with: Claude Code, Claude apps, OpenAI Codex, GitHub Copilot, Cursor, Gemini CLI, Kiro, OpenCode, Goose, Amp, Roo Code, JetBrains Junie, Factory Droid, Devin (ex-Windsurf), Mistral Vibe, OpenHands, Letta

“Works with” means the tool reads the open Agent Skills format; a skill written for one tool may use features others lack.

Needs: Claude Code frontmatter

Security

No issues found by our static scan· No issues found

A static scan is not a guarantee. Skills are third-party content: review a skill before you let an agent use it.

Attribution and licence

Published by
Anthropic
Publisher
Anthropic (Official)
Source
anthropics/knowledge-work-plugins · engineering/skills/deploy-checklist · commit e050c2e
Licence
Apache License 2.0 (redistribution allowed)
  • LICENSE (added by AutoGineer from LICENSE)
  • ATTRIBUTION.md (written by AutoGineer)
Synced

AutoGineer is not affiliated with or endorsed by Anthropic.

Download ZIP

The ZIP holds the skill’s files, its licence files and an ATTRIBUTION.md. Download deploy-checklist.zip