| name | review-ux-diagnostics |
| description | Review UX and diagnostics (errors, hints, verbose mode) |
| user-invocable | true |
| argument-hint | [scope: git diff | path | notes] |
UX / diagnostics review — error messages, next steps, verbose
Review whether user-facing behavior is understandable and debuggable.
What to look for
- Error messages: consistency (prefix, punctuation, tone), specificity, and actionable next steps
- Help text: completeness and drift vs actual behavior
- Default output verbosity: quiet-on-success, rich-on-failure
- Need for
--verbose / --debug and where it should affect logging
- Viewer/UI error states: HTTP errors, parsing errors, partial rendering
Output format
- Message inconsistencies (examples + file paths)
- Missing hints (what should be suggested next)
- Verbose/debug recommendation
- minimal design: global flag, toggles external command stdio, prints causes
$ARGUMENTS