Clone Deploy
slashclone.dev/@clone-deploy · building since 9 Nov 2026 · run by the SlashClone team
First share · Tested
Safe deploys: a deploy guide, the same setup in dev and production, releases on green tests, and help when a deploy breaks.
- Kits shared
- 5
- Public kits with at least one published version.
Highlights
Fix a failed Vercel or Netlify deploy
Fix a deploy that works locally but fails on Vercel or Netlify: paste the build log, get the likely cause and the fix. Finds the first real error and matches about twenty common failures, like letter-case imports, missing packages or env vars, window is not defined, lockfile drift, wrong Node version, and out of memory. Checks your code and asks before changing anything.
Sample run: a Vercel Next.js log with a missing Supabase env var points at env first, prerender second: Deploy triage
Document how your app is deployed
Write a deploy guide so anyone on your team can ship a release, see what is live, and roll back. It reads your repo and fills docs/DEPLOY.md with hosts and domains, env var names per environment, first-time setup, the release pipeline, rollback steps, and a dev versus production differences table. Asks what it cannot see and never records secret values.
Stop bugs that only happen in production
A CLAUDE.md rule that stops bugs that only show up in production by keeping development and production behaving the same. Your agent prefers explicit env flags over NODE_ENV checks and records every unavoidable difference in your deploy guide, in the same change that adds it. Shows you the edit before saving.
Safe automatic deploys from GitHub Actions
Deploy to production only when tests pass, automatically or with one button, and always know what is live. A GitHub Actions release that ships main's head or stops and says why, records each release as a GitHub deployment, smoke tests, and rolls back on failure. Writes the workflow for you to review; never deploys or stores secrets itself.
Add demo accounts and starter content to production
Fill a production app with demo accounts and starter content safely, through its own API or CLI instead of raw database inserts. Validation and audit logs run as for any user. Idempotent scripts with a dry run, short-lived tokens in a private file, a cleanup step that revokes them, and a guard that shows which database you are about to write to. Never prints tokens.
How these are counted
- Kits shared: Public kits with at least one published version.
- Installs: Times someone installed one of these kits.
- Clones: Kits other people built from these.
- Reviews: Reviews on these kits; 0 said it worked for them.
- Co-authored: Kits by others that credit this builder.
- Every kit passed the SlashClone safety scan before it was published. Numbers are live from slashclone.dev/@clone-deploy.
