deploy-checklist
Skill0 starsChanged 6 months agoMITView on GitHub
Use before pushing to a deployed environment (staging or prod). Walks through env vars, migrations, secrets, build, and rollback prep.
- Reads credentials
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
Used with
Projects with it also use tdd and grill-me.
Other files people use alongside this one.
Files found in the same public projects as a version of this one, more often than they turn up anywhere else. Each project counts once, large collections count for less, and this file's own repository is left out.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
- IcodeNet/agent-skills★ 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 repository7 other files it gives its agents.
- AGENTS.mdAGENTS.md
- CLAUDE.mdCLAUDE.md
- .github/copilot-instructions.mdCopilot instructions
- add-resourceSkill
- onboard-an-agentSkill
- remove-demo-codeSkill
- self-correcting-loopSkill
The file
We split this skill into the rules it gives an agent
6 rules. 0 are common, 4 are distinctive, and 2 are very specific to this project.
0
Common
Most of the 14 edited versions we read keep these.
4
Distinctive
This author's own choices. Worth a look.
2
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Distinctive: line 8
Run through this before every deploy.
- Very specific: line 12
Every variable in example.env must exist in the deploy target with a real value:
- Distinctive: line 18
Run on your local machine pointing at the prod env (carefully):
- Distinctive: line 25
If that errors, fix the connection string before deploying.
- Distinctive: line 41
If gitleaks finds anything in history, stop.
- Very specific: line 43
Check .env is in .gitignore:
“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
Run through this before every deploy. Skipping it is how outages happen.
1. Environment variables
Every variable in example.env must exist in the deploy target with a real value:
DATABASE_URL— points at the production Postgres (not local!)PORT— matches what the platform expects (usually set by the platform itself)NODE_ENV=production
Run on your local machine pointing at the prod env (carefully):
# Confirm the deployed app can reach the prod DB.
DATABASE_URL="<prod url>" npx prisma db pull --print | head -20If that errors, fix the connection string before deploying.
2. Database migrations
DATABASE_URL="<prod url>" npx prisma migrate deploymigrate deploy is the only command safe for production — it never resets, never prompts. Never run migrate dev against prod.
3. Secret hygiene
npx gitleaks detect --no-bannerIf gitleaks finds anything in history, stop. Rotate the leaked credential and force-push only after coordinating with the user. Hardcoded secrets are the #1 cause of preventable breaches.
Check .env is in .gitignore:
git check-ignore .env # must print ".env"4. Build
npm run buildBoth the client (vite build) and server (tsc -p tsconfig.server.json) must build clean. If either errors, deploy fails — fix locally first.
5. Run the full guardrail pass
npm run typecheck && npm run lint && npm run lint:unused && npm run test:runCI does this too, but running locally first catches issues before they waste deploy time.
6. Smoke test the build
NODE_ENV=production node dist/server/index.js
# In another terminal:
curl http://localhost:3001/api/health{ "status": "ok", "env": "production" } means the server started cleanly. Hit a tRPC endpoint too:
curl http://localhost:3001/trpc/contact.list7. Rollback plan
Know how you'll roll back before you deploy:
- Platform redeploy of previous build (most platforms: 1 click)
prisma migrate resolve --rolled-back <migration-name>if a migration corrupted state- DB backup snapshot before the deploy (use the platform's built-in snapshot)
Checklist
- Prod env vars set and verified
prisma migrate deploysucceededgitleaks detectclean.envis in.gitignorenpm run buildsucceeds locallytypecheck,lint,lint:unused,test:runall pass- Smoke test against production build succeeds
- DB snapshot taken; rollback path identified
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.

