Pre-deployment validation for $ARGUMENTS environment:
- Tests: Run full test suite, all must pass
- Git status: Check for uncommitted changes across all repos
- Schema sync: Verify the project's ORM/DB schema definition matches expectations (e.g. Prisma schema, Django models, Rails schema.rb, migrations directory)
- Secrets check: Scan for hardcoded credentials, API keys, passwords
- Dev artifacts: Check for language-appropriate debug/print statements (console.log, print(), System.out.println, fmt.Println, etc.), debugger statements, TODO/FIXME in production paths
- Env vars: Verify required environment variables are documented
- Auth coverage: Validate all API endpoints have auth middleware
- Dependency audit: Run the ecosystem's dependency audit (
npm audit/yarn audit,pip-audit,bundle audit,cargo audit,govulncheck, etc., detected from the manifest/lockfile). Classify: CRITICAL/HIGH (action required) vs MODERATE/LOW (note). Separate production vs dev-only vulnerabilities. Check for auto-fixable with--dry-run. - Build: Verify project builds without errors
- Migration safety: Check if any ORM models/migrations are missing (risk of tables dropped by destructive sync)
If argument is "audit" → run only step 8 (dependency vulnerability scan) across the current project.
GO/NO-GO Criteria
- NO-GO: Any test failure, hardcoded secret found, ORM model/migration missing, build failure, or CRITICAL/HIGH vulnerability in production deps
- GO: All steps pass. MODERATE/LOW vulnerabilities in dev-only deps are acceptable with note.
- GO with warnings: All critical steps pass but non-blocking issues exist (dev-only vulns, TODO items in non-critical paths)
Output: GO / NO-GO status with detailed checklist results.
