Apply database migrations cleanly
Run migrations, fix schema or SQL errors, and repeat until prisma migrate status reports clean, capped at 6 turns.
/goal all database migrations apply cleanly — run them, fix schema or SQL errors, repeat until `npx prisma migrate status` is clean; stop after 6 turns
claude-code · codex
Implementation note
Point it at a development database, never production. Prisma-flavored, but the pattern maps to any migration tool with a status command.
More database loops
N+1 query hunt
Instrument the test suite with query logging, find endpoints issuing N+1 queries, and fix them with eager loading or batching until the hot paths are clean.
/goal no endpoint in the integration test suite issues more than 10 SQL queries per request — enable query logging in the test environment, find the worst N+1 offender, fix it with eager loading or a batched query, verify the count dropped and tests still pass, then move to the next; stop after 12 turns
databasemedium risk
Clean production data to spec
Remove disallowed records, sharpen the classification logic, and verify the remaining dataset against an explicit definition.
Review production records, remove anything that does not meet the allowed definition, improve the classification logic, and verify the remaining data.
databasehigh risk