Vibe Coding and Database Changes: A Safe Preflight Checklist

Git can restore code files, but it cannot necessarily restore deleted records. Before letting an AI agent change data or a database schema, plan a separate recovery path.

Code rollback is not a database restore

Returning to an earlier app version changes code. Restoring data depends on a database backup or log and can put a project into a state that differs from the current one. They are separate operations with separate consequences.

Version control can roll back code; data needs its own backup.
Restoring a copy may remove newer records or cause downtime.
Separate uploaded files and storage objects may not be included in a database backup.

Prepare a safe place to make the change

Start by naming the tables, records, and users that should be affected. For real data, make a copy or use staging first, then check your provider’s actual backup coverage and retention.

State the environment: local, staging, or production.
Create a backup before the change and verify that it can be restored.
Use test data without private information.
Never give an AI agent production database credentials.

Ask the AI for a plan before execution

Ask it to explain the proposed change and show the query or migration first. A person should verify the scope, each operation, and possible side effects. “It should work” is not enough for a delete or bulk update.

Name which rows may change and which must stay untouched.
Ask for a count of affected rows before any write.
Check the conditions, constraints, repeatability, and undo plan.
Do not run a destructive migration in production without a verified recovery plan.

Verify the result and the way back

After a staging run, compare record counts and samples, app behavior, and error logs. A backup helps only when you know what it includes and how to restore it without surprises.

Check successful, boundary, and rejected cases.
Confirm deployments work with both the old and new schema where needed.
Record the backup time, recovery owner, and expected downtime.
If you cannot verify restoration, get help before changing production data.

Vibe Coding and Database Changes: A Safe Preflight Checklist

Code rollback is not a database restore

Prepare a safe place to make the change

Ask the AI for a plan before execution

Verify the result and the way back

Primary sources