Catch schema drift nightly
Every night at 3am, dump the production schema and diff it against migrations, filing issues for any drift found.
/schedule every night at 3am, dump the live database schema (`pg_dump --schema-only`) and diff it against the schema produced by applying all committed migrations to a fresh scratch database. Verify the scratch build reports `migrate status` clean before comparing. Any drift — columns, indexes, or constraints present in prod but missing from migrations, or vice versa — gets an issue filed with the exact diff attached and a proposed corrective migration for human review. Read-only against production; never modify the live schema. Stop after 1 pass per run.
claude-code
Source: looprepograded A · 100/100 — how grades work →
More database loops
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
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
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.