/reportbug Command

/reportbug is an invaluable tool when you encounter unexpected behavior with Bwat. Instead of manually compiling all the technical details required for a proper bug report, this command transforms Bwat into your personal issue documentation assistant.

It systematically guides you through collecting comprehensive troubleshooting information and automatically submits a perfectly formatted GitHub issue with all relevant system specifications included.

Using the /reportbug Command

When you experience unexpected behavior:

1. Type /reportbug in the chat interface
2. Bwat will walk you through documenting:
   • A concise title summarizing the issue
   • Expected versus actual behavior
   • Detailed reproduction steps
   • Relevant error messages or output
   • Additional contextual information
3. Review the complete report before submission
4. Confirm to automatically generate a properly formatted GitHub issue including:
   • Your provided details
   • System configuration
   • Bwat version information
   • Environment specifications

Practical Example

Recently I encountered an issue where Bwat was unresponsive when processing large codebases. Rather than manually gathering troubleshooting information, I simply entered /reportbug and followed the intuitive prompts.

Bwat helped me clearly document:

• The specific file operations I was attempting
• The unexpected timeout behavior
• The exact sequence that triggered the issue
• Relevant console warnings

Within moments, a comprehensive GitHub issue was automatically generated - complete with my system specs, Bwat version, and Node.js environment details - saving me valuable troubleshooting time.