Error Handling Review
Finds every path that swallows an error, leaves state half-written, or reports success after failing.
Free — no card needed
Create a free account
to open Error Handling Review — and the other 364 prompts across 21 categories.
Already have an account?
Running it, start to finish
- Paste the code with what state it writes and what calls it.
- Fix the partial-write findings first.
- Add a test for each error path you repaired.
What you get back
The output this produces, every time.
- Traces every multi-write operation to say what state a mid-way failure leaves.
- Finds functions that return success after something inside them failed.
- Checks resource cleanup on the throwing path, not just the normal one.
Getting better results
Where this usually goes wrong, and how to avoid it.
- Describe what the code writes. Section 2 is the highest-value part and it needs to know what state is touched, in what order.
- Check batch operations carefully. Partial batch failure reported as success is common, damaging and almost never handled on the first pass.
- Turn each finding into a test. Error paths are the least-tested code in most projects, which is exactly why they contain these bugs.
More Coding prompts
All Coding →- Coding
Review for the Bug, Not the Style
A code review that hunts correctness failures and states the exact input that breaks each one, instead of listing naming preferences.
ClaudeChatGPTGemini000Open → - Coding
Database Migration Plan
Plans a schema change that ships without downtime, in steps that are each independently safe and reversible.
ClaudeChatGPT000Open → - Coding
Refactor With a Safety Net
Plans a refactor as a sequence of individually safe, individually shippable steps, with the characterisation tests that make each one verifiable.
ClaudeChatGPT000Open →
Written for The AI University. Every prompt in this library is original work — authored, tested and revised here, not collected from elsewhere. 365 of them, free with an account.