Deployment env handoff
Skill codezelat/codezela-web-skills/skills/deployment-env-handoff
Production-grade web development skills for AI coding agents.
npx -y skills add codezelat/codezela-web-skills --skill deployment-env-handoffAssembled from the repository path, not quoted from the project. Check it against their README if it does not work.
One thing to look at
- 0 stars0 stars. Stars are a popularity signal and not a quality one, but at this level it is likely that nobody has read this closely except its author, and you would be relying on your own review.
What its author says it does
Copied from the file, not written here
Use when preparing or auditing deployment readiness, Vercel, env vars, .env.example, README, AGENTS.md, migrations, live-domain checks, pushed-vs-deployed status, provider setup, no-secrets audits, or launch handoff.
SKILL.md
1.6 KB, as published. Nobody here has run it
Deployment Env Handoff
Use this when local success must become repeatable deployment success.
Non-Negotiables
- Do not put secrets in tracked files.
.env.exampledocuments names and purpose, not real values.- README/AGENTS should match actual scripts and architecture.
- Deployment readiness includes migrations, provider dashboards, storage/email/auth domains, and live URL checks.
- Pushed code is not the same as deployed code; verify the live target when asked.
- Do not leave temporary migration/seed/docs files unless they are intentionally reusable.
Workflow
- Inspect package scripts, build command, output mode, deploy config, env usage, migrations, and provider dependencies.
- Search for secret-like values in tracked files.
- Update
.env.examplewith all required and optional env vars grouped by service. - Update README/AGENTS with setup, migrations, seed, build, deploy, and verification commands.
- Confirm
.gitignorecovers local env, generated private artifacts, and provider dumps. - Run build/lint/typecheck as relevant.
- For Vercel or similar, check custom domain, production URL, runtime env, and migration order.
Handoff Format
- Required env by provider.
- Commands to install, migrate, seed, build, and start.
- Provider dashboard settings still required.
- Verification already run.
- Known environment-dependent items not proven locally.