deploy-checklist
Prepare a release-specific deployment checklist with readiness checks and rollback triggers.
- License 许可
- MIT
- 所属仓库
- meymchen/skills
- 最近更新
- 2026-10-16
- Stars
- ★ 0
- Forks
- 0
01 前言 Front Matter
- name
- deploy-checklist
- description
- Prepare a release-specific deployment checklist with readiness checks and rollback triggers.
- argument-hint
- [service or release name]
- user-invocable
- true
- disable-model-invocation
- true
02 资源文件 1
- 参考文档agents/openai.yaml196 B
03 SKILL.md 正文
<!-- Adapted by Yuming Chen on 2026-10-04 for personal use and dual-host support. See ../../UPSTREAM.md. -->
Deploy Checklist
Read CONNECTORS.md for host invocation, personal use, and optional tools.
Generate a pre-deployment checklist to verify readiness before shipping.
Usage
Claude Code examples are shown below. In Codex, select this plugin's deploy-checklist skill or use $engineering:deploy-checklist with the same request.
/engineering:deploy-checklist [service or release name]
Output
## Deploy Checklist: [Service/Release]
**Date:** [Date] | **Deployer:** [Name]
### Pre-Deploy
- [ ] All tests passing in CI
- [ ] Code reviewed; required approvals obtained (if applicable)
- [ ] No known critical bugs in release
- [ ] Database migrations tested (if applicable)
- [ ] Feature flags configured (if applicable)
- [ ] Rollback plan documented
- [ ] On-call team notified (if applicable)
### Deploy
- [ ] Deploy to staging and verify (if available)
- [ ] Run smoke tests
- [ ] Deploy to production (canary if available)
- [ ] Monitor error rates and latency for the project's observation window
- [ ] Verify key user flows
### Post-Deploy
- [ ] Confirm metrics are nominal
- [ ] Update release notes / changelog
- [ ] Notify stakeholders (if applicable)
- [ ] 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 release changes are merged and any required approvals are present
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 — Save the customized checklist in your project docs to reuse it next time.
- Include rollback criteria — Decide when to roll back before you deploy, not during.
04 同仓库更多 Skills
cleanup-merged-branch
Safely clean a merged local branch, reproducible worktree caches, and stale local branches before updating the repository default branch.
verify-acceptance-items
Verify a GitHub pull request or GitLab merge request (MR) against the acceptance criteria (验收标准/条件, task-list checkboxes) of the issues it links to, then tick the criteria it proves once the user confirms. Use when asked whether a PR or MR is done or meets its issue, when asked to check off an issue's checkboxes, or right after opening or updating a PR or MR that closes an issue.
update-request-body
Update the title and body of one or more GitHub pull requests or GitLab merge requests (MRs).
commit
Create a Git commit from the current changes.
commit-push-request
Commit current changes, push the branch, and open a GitHub pull request or GitLab merge request (MR).
clean-gone
Remove local Git branches whose upstreams are gone, including associated worktrees.