# Database changes during a deploy

Prompt · Agent harness and modern stack · G02

Checks that each database change works with the old code that is still live while a release finishes.

## Prompt

```text
Trace what happens during the deployment window when a new database migration or API schema change goes live while previous client bundles, active background workers, or queue consumers are still running. Identify column renames, non-nullable additions, or contract changes that break backwards compatibility before the old code finishes draining.
```

**What it returns:** Each recent migration checked against the previous release's queries, with any break shown.

**Skip it when:** Changes that touch neither the database layout nor how parts of the app talk to each other.

**Tools:** Repository, migrations folder, previous release tag.

**Changes:** Changes nothing

**Sessions:** One session

## Related

- [Why production might not match main](https://atlasscope.dev/prompts/why-production-might-not-match-main): Lists every way 'merged' can fail to mean 'live'.
- [Settings that differ in production](https://atlasscope.dev/prompts/settings-that-differ-in-production): Finds settings that behave differently in production than anyone expects.
- [Are our database changes safe before we merge?](https://atlasscope.dev/prompts/are-our-database-changes-safe-before-we-merge): A migration, or a change to functions, views, RLS, types or column meaning, is about to ship.

Source: https://atlasscope.dev/prompts/database-changes-during-a-deploy