[Good First Issue]: Improve error messages

[youngcoder45]

Summary

Improve existing error messages to make them more user-friendly and informative.

Context

Current error messages may be unclear, technical, or not helpful for users. Better error messages improve user experience and reduce confusion.

Suggested approach

1. Search for error messages in the codebase (look for throw, return, console.error, etc.)
2. Identify unclear or technical messages
3. Rewrite them to:
   • Be simple
   • Be user-friendly
   • Suggest a possible fix (if possible)
4. Ensure consistency in tone

Acceptance criteria

• Error messages are easy to understand
• No overly technical or vague messages remain
• Messages provide helpful guidance

Files / areas to look at

• Command handlers
• Middleware or validation logic
• Error handling utilities

Checklist

• The scope is small enough for a first contribution.
• Acceptance criteria are clear and testable.
• Relevant pointers/links are included.

[Reyodin-06]

Hey! I'd like to work on improving the error messages. Could you assign this to me?

[youngcoder45]

Hey! I'd like to work on improving the error messages. Could you assign this to me?

Yea sure. You can work on it fork the repo and start. @Reyodin-06

[shivani-d-13]

Hi, I’ve opened a PR improving error messages in codebuddy_quiz: #34
Happy to extend similar improvements to other commands if that would be helpful.

[youngcoder45]

Looks good

[msohaib422]

Is is still open?

[youngcoder45]

Is is still open?

Yes under review tho