deploy-checklist
Skill0 starsChanged 4 months agoMITView on GitHub
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).
14 other projects use a version of this.
Adopted by
Most recently taken up by
- nisarth/claude-skills-storetheir own version, first seen Nov 8, 2026
- anotherben/claude-harnesstheir own version, first seen Nov 8, 2026
- kitloomlk-stack/devops-cloud-kittheir own version, first seen Oct 15, 2026
- jazzpujols34/claude-skillstheir own version, first seen Oct 13, 2026
- anthropics/knowledge-work-pluginstheir own version, first seen Oct 13, 2026
- johanolofsson72/Claudetheir own version, first seen Oct 2, 2026
Other versions14 projects use a version of this.
Word for word · 0
None found.
Edited · 0
None found.
Wrote their own version · 14
- anthropics/knowledge-work-plugins★ 35ksame name
- hamzafarooq/claude-code-starter★ 145same name
- drafthq/draft★ 40same name
- anotherben/claude-harness★ 7same name
- viknesh20-20/claude-code-tool-kit★ 7same name
- wchen02/cursor-agent-learning★ 3same name
- johanolofsson72/Claude★ 2same name
- lodetomasi/claude-code-training-lab★ 2same name
- nisarth/claude-skills-store★ 1same name
- Avinava/agentic-react-express-ts★ 0same name
4 more not listed
How matches are found. Word for word: the exact same text. Edited: shares passages with this file (“99% same” means 99% of its five-word phrases also appear here; 10% or more counts). Their own version: similar meaning, or, weakest, the same name. We can’t tell which project had it first. Projects are counted among the 200 most-starred candidates, and mentions are links to the repository we found, up to 50 per site, so both counts are a floor.
In this repository40 other files it gives its agents.
- address-pr-feedbackSkill
- architectureSkill
- code-reviewSkill
- code-structureSkill
- competitive-briefSkill
- contract-guardSkill
- debugSkill
- deep-workSkill
- dependency-upgradeSkill
- diagnoseSkill
- documentationSkill
- explain-pr-step-by-stepSkill
- feedback-checkpointSkill
- grill-meSkill
- grill-with-docsSkill
- handoffSkill
- improve-codebase-architectureSkill
- incident-responseSkill
- memory-managementSkill
- observabilitySkill
- plan-criticSkill
- plan-from-rfcSkill
- pr-babysitterSkill
- prototypeSkill
- queue-checkSkill
- rebase-onto-mainSkill
- releaseSkill
- security-reviewSkill
- setup-engineering-skillsSkill
- squash-and-pushSkill
- synthesize-researchSkill
- system-designSkill
- tddSkill
- tech-debtSkill
- testing-strategySkill
- to-issuesSkill
- to-prdSkill
- triageSkill
- verification-before-completionSkill
- zoom-outSkill
The file
We split this skill into the rules it gives an agent
2 rules. 0 are common, 2 are distinctive, and 0 are very specific to this project.
0
Common
Most of the 14 edited versions we read keep these.
2
Distinctive
This author's own choices. Worth a look.
0
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Distinctive: line 24
No production deploy without a stated rollback path.
- Distinctive: line 25
Do not treat “works on my machine / staging” as sufficient without post-deploy verification.
“Common” is measured: kept by at least 6 in 10 of the 14 edited versions of this file we could read. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Files
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
Does it work?
Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.
No reviews yet
People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.
- It worked
- Partly
- It didn't
Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.
Your trail
Files you open will collect here, so you can find them again.
Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.
Now do this for your own.
Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.