Deploy checklist
Pre-deploy and release checklist with rollback planning. Use when deploying, releasing, shipping, or preparing a pre-deploy review. Do not use for coding the feature itself or for live incident command (use incident-response).From its SKILL.md
npx -y skills add IcodeNet/agent-skills --skill deploy-checklistAssembled from the repository path, not quoted from the project. Check it against their README if it does not work.
One thing to look at
- 0 stars0 stars. Stars are a popularity signal and not a quality one, but at this level it is likely that nobody has read this closely except its author, and you would be relying on your own review.
SKILL.md
1.5 KB, 283 tokens by cl100k_base, as published. Nobody here has run it
Deploy Checklist
Ship safely: verified build, observable release, reversible plan.
Workflow
- Pre-flight — complete
references/preflight.md(quality, security, config, docs). If the release changes any externally consumed surface, confirm thecontract-guardcompatibility statement exists; for versioned releases, notes and version bump per thereleaseskill. - Rollback plan — write it before deploy (flag kill-switch, previous artifact, migration reverse).
- Deploy — prefer staged rollout (staging → canary/partial → full) when available.
- Watch — first-hour checks: health, error rate, latency, one critical user flow.
- Decide — advance, hold, or roll back using explicit thresholds.
- Close out — changelog/notes; remove temporary flags when safe; file follow-ups.
Constraints
- No production deploy without a stated rollback path.
- Do not treat “works on my machine / staging” as sufficient without post-deploy verification.
- Migrations: know whether they are backward-compatible with the currently running app.
Verification
- Preflight checklist green or exceptions documented
- Rollback plan written
- Post-deploy health + critical flow verified
- Go/hold/rollback decision recorded
What ships with it: 1 file
792 B alongside SKILL.md
references/
- preflight.md792 B