deploy-check

Steps

1. Check what's being pushed

git status
git diff origin/main...HEAD --stat
git log origin/main..HEAD --oneline

2. TypeScript check (if applicable)

tsconfig.json

npx tsc --noEmit

tsconfig.json

frontend/

3. Check for accidentally staged secrets

git diff --cached --name-only | grep -iE '\.env|secret|key|credential|token|password'

git diff --name-only | grep -iE '\.env'

4. Dependency / schema changes

• Look for migration files (common patterns:

  migrations/

  ,

  schema.sql

  ,

  *.migration.ts

  ,

  db/migrate/

  ). If any changed since last commit, remind user to run migrations before deploying.
• Check

  package.json

  ,

  requirements.txt

  ,

  go.mod

  ,

  Cargo.toml

  — if dependencies changed, flag which ones are new so user can confirm they're available in the production environment.
• If new environment variables appear in the diff (search for

  os.getenv

  ,

  process.env

  ,

  ENV[

  ), list them and ask: are these set in your production environment?

5. Hygiene reminders (not blockers)

• Changelog / release notes: Did anything user-visible ship (new feature, fix, UI change)? If yes, remind them to update their changelog.
• README: Did the setup steps, architecture, or env vars change? If yes, remind them to update the README.
• Docs / API docs: If new endpoints were added, remind them to document them.

6. Output the verdict

✅ TypeScript: no errors
✅ No secrets staged
✅ No migrations pending
✅ Dependencies: no new packages
📝 Changelog: [reminded / not needed]
→ safe to push

❌ TypeScript: 3 errors — fix these first
   src/auth.ts:42 — Property 'user' does not exist on type 'Session'
⚠️  .env.local is staged — remove it before committing
⚠️  schema.sql changed — run migrations in prod first
📝 2 new env vars in diff — confirm they're set in production
→ fix blockers before pushing