deploy-checklist
Skill7 starsChanged 7 months agoMITView on GitHub
Runs a comprehensive pre-deployment verification checklist covering tests, security, environment config, migrations, rollback plan, and breaking changes. Use before deploying to staging or production.
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
- 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
- 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 repository45 other files it gives its agents.
- .claude/CLAUDE.mdCLAUDE.md
- CLAUDE.mdCLAUDE.md
- a11y-auditSkill
- api-designSkill
- architecture-reviewSkill
- business-blueprintSkill
- business-logic-auditSkill
- changelogSkill
- ci-pipelineSkill
- code-coverageSkill
- competitive-analysisSkill
- convert-codeSkill
- create-componentSkill
- db-migrationSkill
- debugSkill
- dependency-auditSkill
- design-flowSkill
- docker-setupSkill
- env-setupSkill
- error-monitorSkill
- estimateSkill
- explain-codeSkill
- fix-issueSkill
- generate-docsSkill
- git-cleanupSkill
- grill-meSkill
- handoffSkill
- legal-pagesSkill
- memory-importSkill
- memorySkill
- microcopySkill
- migrate-frameworkSkill
- onboardSkill
- optimizeSkill
- pr-summarySkill
- refactorSkill
- reference-appSkill
- review-prSkill
- security-scanSkill
- seo-scaffoldSkill
- tddSkill
- web-launch-checkSkill
- wireframeSkill
- write-skillSkill
- write-testsSkill
The file
We split this skill into the rules it gives an agent
1 rule. 0 are common, 0 are distinctive, and 1 is very specific to this project.
0
Common
Most of the 14 edited versions we read keep these.
0
Distinctive
This author's own choices. Worth a look.
1
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Very specific: line 98
If any item in this section fails, run /web-launch-check for a structured audit and /legal-pages or /seo-scaffold to generate the missing …
“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
Pre-Deployment Checklist
Current State
!git branch --show-current 2>/dev/null
!git log --oneline -10 2>/dev/null
!git status --short 2>/dev/null
Verification Checklist
Go through each section. Mark items as PASS, FAIL, WARN, or N/A.
1. Code Readiness
- All changes are committed — no uncommitted work
- Branch is up to date with main/master
- No merge conflicts
- All PRs for this release are merged
- No draft PRs accidentally included
2. Testing
- All unit tests pass
- All integration tests pass
- End-to-end tests pass (if applicable)
- No new test failures compared to main branch
- Edge cases for new features are tested
- Performance-sensitive changes have been load tested
3. Code Quality
- No
console.log/print/ debug statements left in - No
TODOorFIXMEcomments that should be resolved - No commented-out code blocks
- Linting passes with zero errors
- Type checking passes (if applicable)
4. Security
- No hardcoded secrets, tokens, or API keys
- No new dependencies with known vulnerabilities
- Input validation in place for new endpoints
- Authentication/authorization checked for new routes
- CORS configuration is correct for the target environment
5. Database & Migrations
- All migrations are created and tested
- Migrations are backwards compatible (can rollback)
- No destructive migrations without data backup plan
- Indexes added for new queries
- Migration order is correct
6. Configuration & Environment
- All new environment variables are documented
- Environment variables are set in target environment
- Feature flags are configured correctly
- Third-party service configs are updated (if needed)
- SSL/TLS certificates are valid
7. API & Breaking Changes
- No breaking API changes without versioning
- API documentation is updated
- Deprecation notices added for removed features
- Consumers (frontend, mobile, third-party) are notified
8. Monitoring & Observability
- Logging is adequate for new features
- Error tracking covers new code paths
- Alerts configured for critical paths
- Dashboards updated if needed
9. Rollback Plan
- Rollback steps are documented
- Database rollback migration tested
- Feature flags can disable new features without rollback
- Previous version is tagged and accessible
10. Web Compliance & SEO (skip ONLY if not a public website)
- Privacy Policy live at
/privacyand linked in footer - Terms of Service live at
/termsand linked in footer (if signup/payments) - Cookie Policy + cookie consent banner present (if any non-essential cookies)
- No tracking scripts load before user consent
sitemap.xmlaccessible at site root and lists all canonical URLsrobots.txtaccessible at site root with sitemap reference- Production environment NOT disallowed in
robots.txt(common deploy bug) - Every page has unique
<title>and<meta description> - Every page has canonical URL, Open Graph tags, Twitter Card tags
- 404 page returns HTTP 404 (not 200)
- HTTPS-only with HSTS header
- WCAG 2.1 AA verified (contrast, keyboard, focus, alt text)
- Core Web Vitals within budget (LCP ≤ 2.5s, INP ≤ 200ms, CLS ≤ 0.1)
- If applicable: GDPR/CCPA "Do Not Sell" link, DSAR endpoint, consent records retained
If any item in this section fails, run /web-launch-check for a structured audit and /legal-pages or /seo-scaffold to generate the missing pieces.
Output
Summary Table
| Category | Status | Issues |
| Code Readiness | PASS/FAIL | ... |
| Testing | PASS/FAIL | ... |
| ... | ... | ... |
Blocking Issues
List any FAIL items that must be resolved before deployment.
Warnings
List any WARN items that should be addressed but aren't blocking.
Deploy Verdict
- READY — All checks pass, safe to deploy
- CONDITIONAL — Deploy after resolving blocking issues
- NOT READY — Significant issues require more work
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.

