- Create
CONTRIBUTING.md
with clear guidelines for contributors - Create issue templates for GitHub:
- Bug report template
- Feature request template
- Question/support template
- Implement secure API key storage
- Move from plaintext
.env
to more secure storage - Document best practices for API key management
- Move from plaintext
- Add example configuration with sensitive values redacted
- Create fallback mechanisms for when API access fails
- Document security practices for users
- Add more unit tests to increase coverage
- Set up integration tests for different LLM providers
- Create a GitHub workflow for automated testing on PRs
- Verify Completion Of User Documentaiton
- Run manual testing on different environments:
- Linux (Ubuntu, Fedora)
- macOS
- Windows (WSL and native)
- Add version checking and update notification mechanism
- Make sure users can easily update the tool
- Fix handling of multi-line commit messages
- Implement proper command feedback when API calls fail
- Add clear error messages for common configuration issues
- Make personality system more customizable
- Improve Terminal Output formatting where possible
- Scripts for versioning and others currently still have very messy logs/output. -> Make sure to cleanup spammy logs from any scripts
- Create semantic versioning strategy
- Set up proper release workflow with changelogs
- Add version badges to README
- Set up project discussions on GitHub
- Create project roadmap visible to community
- Document initial architecture for plugins
- Create examples for future plugin developers
- Define plugin interface specifications
- Audit code for hardcoded values or personal references
- Clean up any debug code or TODOs
- Create a pre-release checklist
- Check license compatibility for all dependencies
- Prepare announcement strategy for the release
- Set up repository social previews and badges