Getting Help
Need assistance with Vibesweep? Here's how to get help quickly.
Support Channels
1. Documentation
Start with our comprehensive docs:
2. Community Support
GitHub Discussions
- Ask questions and share tips
- github.com/jeffweisbein/vibesweep/discussions
Discord Community
- Real-time chat with other users
- Direct access to maintainers
- Join at: discord.gg/vibesweep (Coming soon!)
3. Issue Reporting
Bug Reports Report bugs on GitHub Issues:
Include:
- Vibesweep version (
vibesweep --version
) - Node.js version (
node --version
) - Operating system
- Error messages
- Steps to reproduce
Feature Requests
Submit feature ideas with the enhancement
label.
4. Pro Support
Email Support Pro customers get priority email support:
- Email: support@vibesweep.ai
- Response time: Within 24 hours
- Include your license key
Enterprise Support Custom support packages available:
- Dedicated Slack channel
- Video consultations
- Custom feature development
- Contact: enterprise@vibesweep.ai
Before Asking for Help
1. Check Your Version
# Ensure you're on the latest version
npm update vibesweep
vibesweep --version
2. Review Error Messages
# Run with verbose logging
vibesweep analyze . --verbose
# Check for common issues
vibesweep doctor
3. Minimal Reproduction
Create a minimal example that reproduces the issue:
# Create test directory
mkdir vibesweep-test
cd vibesweep-test
# Add minimal code that shows the problem
echo "const unused = 'test';" > test.js
# Run analysis
vibesweep analyze . --verbose
Debugging Tips
Enable Debug Mode
# Set debug environment variable
DEBUG=vibesweep:* vibesweep analyze .
# Save debug output
DEBUG=vibesweep:* vibesweep analyze . 2> debug.log
Check Configuration
# Validate config file
vibesweep config validate
# Show effective configuration
vibesweep config show
Common Solutions
Permission Errors
# Fix npm permissions
npm config set prefix ~/.npm-global
export PATH=~/.npm-global/bin:$PATH
Module Not Found
# Reinstall dependencies
rm -rf node_modules package-lock.json
npm install
Out of Memory
# Increase memory limit
NODE_OPTIONS="--max-old-space-size=4096" vibesweep analyze .
Contributing
Report Documentation Issues
Found an error in the docs?
- Click "Edit this page" on any doc page
- Submit a pull request with fixes
Contribute Code
See our Contributing Guide
Share Your Experience
- Write blog posts about using Vibesweep
- Share on social media with #vibesweep
- Give a talk at your local meetup
Stay Updated
Release Notes
Social Media
- Twitter: @vibesweep
- LinkedIn: Vibesweep Updates
Newsletter
Subscribe for updates and tips:
Quick Links
- Report a Bug: GitHub Issues
- Request a Feature: GitHub Issues
- Pro Support: support@vibesweep.ai
- Security Issues: security@vibesweep.ai
Remember: The more details you provide, the faster we can help!
Related
- FAQ - Frequently asked questions
- Common Issues - Known issues and solutions
- Community Guidelines - Be kind!