Check Error Messages for Actionability
Added 2026-11-01
After reading the error, does the user know what to do next?
Here is a set of error messages from my system. Check each: 1) does it say what happened, or only show a code; 2) does the user know what to do next; 3) rewrite it — what happened, likely cause, actionable step, who to contact; 4) mark which messages should be merged and which split; 5) flag the one most likely to cause a wrong action, such as resubmitting. Do not change the error codes.
Site original
Chinese original
How to use
错误信息的成功标准是「用户知道下一步」。
Try tweaking it
- Have it restate requirements and constraints before writing code.
- Ask for the smallest change plus a rollback path, not a full-file rewrite.
What you should get
- A minimal, runnable change with copy-ready code
- Impact list: which files and call sites must follow
Common mistakes
- Asking it to touch ten files at once, then losing track of what broke what.
- Pasting only the error, with no code or version, and getting an unfixable answer.
How to check the output
- The change runs, can be rolled back, and touches nothing unrelated.
- Edge cases (empty, oversized, concurrent) are covered or explained.
Where it works
- Good for: having it restate requirements and constraints, then propose the smallest runnable change.
- Watch out: include versions and a minimal reproduction with the error, or the fix may look plausible but not fit.