anthropics/knowledge-work-plugins

deploy-checklist

Pre-deployment verification checklist.

Zobacz źródło

Jak używać

  1. Skopiuj polecenie instalacji i sprawdź źródła przed instalacją we własnym środowisku agenta.
  2. W oryginale sprawdź wymagane narzędzia, dane dostępowe i obsługiwane środowiska.
  3. Opisz dane wejściowe i oczekiwany rezultat; porównaj wynik ze źródłami.
npx skills add https://github.com/anthropics/knowledge-work-plugins --skill deploy-checklist

Przed rozpoczęciem

  • Instalacja nie obejmuje subskrypcji modelu, limitu API ani uprawnień do plików.
  • Gwiazdki i instalacje pokazują aktywność, a nie niezależny test jakości lub bezpieczeństwa.
Oryginalny dokument Skill

Treść z repozytorium z zachowaniem nagłówków, przykładów, kodu, tabel, linków i obrazów.

/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

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

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.

Powiązane zadania

z tego samego repozytorium

Więcej Skills

Wszystkie Skills
anthropics
Oficjalne

data-visualization

Create effective data visualizations with Python (matplotlib, seaborn, plotly). Use when building charts, choosing the right chart type for a dataset, creating publication-quality figures, or applying design principles like accessibility and color theory.

instalacje
3
GitHub Stars
31,6 tys.
Aktualizacja
22 paź
anthropics
Oficjalne

ux-copy

Write or review UX copy — microcopy, error messages, empty states, CTAs. Trigger with "write copy for", "what should this button say?", "review this error message", or when naming a CTA, wording a confirmation dialog, filling an empty state, or writing onboarding text.

instalacje
3
GitHub Stars
31,6 tys.
Aktualizacja
22 paź
anthropics
Oficjalne

daily-briefing

Morning rundown - today's meetings with account context, opps closing soon with stale flags, waiting customer emails, and the day's top actions. Use when the user says "daily briefing", "daily brief", "morning briefing", "what's my day", "what's on my plate today", "prep my day", "start my day", "morning rundown", or on a schedule.

instalacje
2
GitHub Stars
31,6 tys.
Aktualizacja
22 paź
anthropics
Oficjalne

incident-response

Run an incident response workflow — triage, communicate, and write postmortem. Trigger with "we have an incident", "production is down", an alert that needs severity assessment, a status update mid-incident, or when writing a blameless postmortem after resolution.

instalacje
2
GitHub Stars
31,6 tys.
Aktualizacja
22 paź