We're here to help you get the most out of CommitWeave! This guide will direct you to the right resources for your specific needs.
First time installing CommitWeave?
-
Check Prerequisites:
node --version # Should be >= 18.0.0 npm --version # Should be >= 8.0.0 git --version # Any recent version
-
Common Installation Fixes:
# Clear npm cache npm cache clean --force # Install with verbose logging npm install -g @typeweaver/commitweave --verbose # Alternative: Use npx npx @typeweaver/commitweave --version
-
Permission Issues (macOS/Linux):
# Fix npm global permissions sudo chown -R $(whoami) ~/.npm-global npm config set prefix '~/.npm-global'
Extension not working properly?
-
Verify Extension Installation:
- Open VS Code Extensions (Ctrl+Shift+X)
- Search "CommitWeave" and ensure it's installed
- Check for any error notifications
-
CLI Detection Issues:
# Test CLI availability commitweave --version # Or try with npx npx @typeweaver/commitweave --version
-
Restart Required:
- Restart VS Code after installing the CLI
- Reload window: Ctrl+Shift+P → "Developer: Reload Window"
- Main README: https://github.com/GLINCKER/commitweave
- Contributing Guide: CONTRIBUTING.md
- VS Code Extension: vscode-extension/README.md
- Security Policy: SECURITY.md
- Getting Started: Step-by-step setup guide in main README
- Configuration Examples: Various config scenarios
- AI Integration: Setting up OpenAI/Anthropic providers
- Team Workflows: Best practices for teams
Please try these steps first:
-
Update to Latest Version:
npm update -g @typeweaver/commitweave # Check VS Code extension for updates too -
Check Existing Issues:
- Search GitHub Issues
- Look for similar problems and solutions
-
Clear Configuration:
# Test with default settings commitweave --help
| Issue Type | Where to Go | Response Time |
|---|---|---|
| 🐛 Bugs | GitHub Issues | 2-3 days |
| 💡 Feature Requests | GitHub Issues | 1 week |
| ❓ Questions | GitHub Discussions | 1-2 days |
| 🔒 Security Issues | security@glincker.com | 24 hours |
Help us help you by providing:
- CommitWeave version:
commitweave --version - Node.js version:
node --version - Operating System: Windows 11, macOS 13, Ubuntu 22.04, etc.
- Error messages: Full stack traces if available
- Steps to reproduce: What you did before the issue occurred
- Expected vs Actual behavior: What should happen vs what happened
Best for: Questions, feature discussions, sharing tips
- Q&A: Get help from the community
- Ideas: Discuss potential features
- Show & Tell: Share your CommitWeave setups
Visit: https://github.com/GLINCKER/commitweave/discussions
- Be respectful and helpful to other users
- Search first before posting duplicate questions
- Provide context when asking for help
- Share solutions when you figure things out
For private or urgent matters:
- General Support: support@glincker.com
- Security Issues: security@glincker.com
- Business Inquiries: contact@glincker.com
- Security Issues: < 24 hours
- General Support: 1-3 business days
- GitHub Issues/Discussions: 1-7 days (varies by complexity)
# Solution 1: Check PATH
echo $PATH | grep npm
# Solution 2: Use npx
npx @typeweaver/commitweave
# Solution 3: Reinstall globally
npm install -g @typeweaver/commitweave# Make sure you're in a git repository
git status
# Initialize if needed
git init# Stage your changes first
git add .
# Or stage specific files
git add filename.js- Install CLI globally:
npm install -g @typeweaver/commitweave - Restart VS Code
- Check VS Code's integrated terminal can run:
commitweave --version
# Check your API key is set
echo $OPENAI_API_KEY
echo $ANTHROPIC_API_KEY
# Test with mock provider
commitweave --ai-provider mockCommitWeave is slow?
- Check startup time:
time commitweave --version - Clear npm cache:
npm cache clean --force - Update Node.js to latest LTS version
- Check network connectivity for AI features
- Git Basics: Learn git fundamentals first
- Conventional Commits: Understanding the commit format standard
- Command Line: Basic terminal/command prompt usage
- Configuration: Custom commit rules and emoji settings
- AI Integration: Setting up and optimizing AI providers
- Team Setup: Configuring CommitWeave for team workflows
- CI/CD Integration: Using CommitWeave in automated workflows
Need help setting up CommitWeave for your team?
- Configuration advice for team standards
- Best practices for large codebases
- Integration guidance with existing workflows
For custom integrations or features:
- Contact business@glincker.com
- Describe your specific needs
- We'll discuss options and pricing
- Acknowledgment: We'll confirm we received your request
- Investigation: We'll reproduce and analyze the issue
- Updates: Regular communication on progress
- Resolution: Fix, workaround, or explanation
- Follow-up: Ensure the solution works for you
- 🚨 Critical: Security issues, data loss
- 🔴 High: Major features broken, blocking work
- 🟡 Medium: Minor issues, workarounds available
- 🟢 Low: Enhancement requests, minor bugs
- Answer questions in GitHub Discussions
- Improve documentation with your learnings
- Share solutions you discover
- Report issues you encounter
Found something missing from this support guide?
- Open an issue with suggestions
- Submit a PR with improvements
- Email us with feedback
🧶✨ We're here to help you succeed with CommitWeave!
Maintained by GLINR STUDIOS
Primary Support: support@glincker.com
Community: GitHub Discussions