What problem does it solve? When drizzle-kit generate or push encounters an ambiguous schema diff (a rename that could be a drop-plus-create) or a destructive change (dropping a non-empty table, recreating a SQLite table), it halts with status: 'missing_hints' and refuses to proceed. This Skill explains how to read the unresolved array and construct the correct Hint reply array so the migration can complete. ## Core Features & Use Cases - Rename-vs-create disambiguation: Build rename or create hints with the correct entity-tuple arity for every kind (table, column, index, foreign key, privilege, and more). - Data-loss approvals: Construct confirm_data_loss replies that echo kind and entity while dropping the runtime-only reason fields. - CLI and SDK retry paths: Pass hints via --hints, --hints-file, or the SDK hints option, with identical Hint shapes on both surfaces. - Use Case: A push against SQLite returns a rename_or_create for a column plus a confirm_data_loss for add_not_null; you build a two-item hints file, re-run with --hints-file, and the push succeeds. ## Quick Start Ask the AI to resolve the missing_hints response from your last drizzle-kit push by building the hints array and retrying the command.