TypeWeaverTroubleshooting
Solutions to common issues and problems when using CommitWeave
Common Issues
Advanced Diagnostics
System Health Check
Run comprehensive diagnostics:
# Full system check
commitweave doctor --verbose
# Network connectivity test
commitweave doctor --check-network
# Configuration validation
commitweave doctor --check-config
# Git repository health
commitweave doctor --check-gitDebug Logging
Enable detailed logging for troubleshooting:
# Enable debug mode
DEBUG=commitweave* commitweave ai --verbose
# Save debug log to file
commitweave ai --verbose --log-file debug.log 2>&1
# Monitor logs in real-time
tail -f ~/.commitweave/logs/commitweave.logEnvironment Information
Gather system information for bug reports:
# System information
commitweave --version
node --version
git --version
uname -a
# Configuration dump
commitweave config --show --verbose
# Git environment
git config --list | grep -E "(user|core|commit)"Getting Help
Self-Help Resources
- Configuration Validation: Run
commitweave doctorfirst - Documentation: Check our CLI Reference and Examples
- Templates: Use proven Configuration Templates
Community Support
- GitHub Issues: Report bugs
- Discussions: Ask questions
- Discord: Real-time community help
Bug Reports
Include this information when reporting bugs:
# System environment
commitweave --version
node --version
npm --version
git --version
echo $SHELL
uname -a
# Error reproduction
commitweave doctor --verbose > system-info.txt
commitweave ai --verbose --dry-run > error-log.txt 2>&1
# Configuration (redact API keys)
commitweave config --show | sed 's/sk-[a-zA-Z0-9]\+/[REDACTED]/g'Still having issues? Open a GitHub Issue with your system information and error logs.