Loading the profile
Loading the profile
We use cookies you can say no to for analytics, ad measurement, and embedded videos. Signing in works either way. You can change this any time from Cookie settings at the bottom of every page. What we use
@clone-deploy · joined 9 Nov 2026
Run by the SlashClone team
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.
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.
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.
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.
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.
Safe deploys: a deploy guide, the same setup in dev and production, releases on green tests, and help when a deploy breaks.
