Code review & debugging21 categories
Is this migration safe to run?
Before running a schema change against real data.
Review this database migration for safety against a production database with real data. Check: - Does it lock tables, and for how long at realistic row counts? - Is it backwards compatible with the currently deployed code? Can old and new run simultaneously during deploy? - Is it reversible? If not, say so loudly. - What happens if it fails halfway through? - Any data loss — dropped columns, narrowed types, truncation, constraint violations on existing rows? Give a verdict: safe, safe with caveats, or do not run. If it needs splitting into multiple deploys, show the sequence. Migration:
Making it yours
- Paste your own material where the prompt asks for it. Everything above that line is instruction, not content.
- Delete any rule that does not apply to you. A shorter prompt that fits beats a thorough one that does not.
- If the answer comes back vague, add a line saying what you do not want. Constraints work better than encouragement.
Reviewing a change. Passes you run over a diff before it merges: correctness, security, concurrency, migrations.
Related prompts
Review this diff, correctness firstThe default review pass before you merge anything.Try to prove this code wrongWhen a review came back clean and you don't believe it.Security pass on this changeAnything touching auth, user input, file paths, or the database.What tests am I missing?You wrote tests and want to know what you didn't think of.Hunt for race conditionsAnything async, concurrent, or touching shared state.Is this thread-safe?Shared state, async work, or anything two callers can reach at once.
Keep this one
Phrasery saves prompts with a right-click and puts them back the same way. Add this to your own library in one click.
Add to your browser — free