Code review & debugging21 categories
What tests am I missing?
You wrote tests and want to know what you didn't think of.
Here is my code and my existing tests. Tell me what is untested. 1. List behaviours the code has that no test asserts. 2. List edge cases missing entirely: boundaries, empty, null, error paths, concurrency. 3. Point out any test that would still pass if the code were broken — tests that assert the wrong thing. 4. Give me the five highest-value tests to add, as actual code. Rank by likelihood of catching a real future bug, not by coverage percentage. Code: Tests:
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.Is this migration safe to run?Before running a schema change against real data.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