- Follow the established ESLint and Prettier configurations
- Use TypeScript for all new code
- Write meaningful commit messages
- Add proper documentation for new features
- Fork the repository
- Create a feature branch
- Make your changes
- Write/update tests
- Submit a pull request
- Update documentation if needed
- Add tests for new features
- Ensure all tests pass
- Update the README.md if needed
- Request review from maintainers
type(scope): subject
body
footer
Types:
- feat: A new feature
- fix: A bug fix
- docs: Documentation only changes
- style: Changes that do not affect the meaning of the code
- refactor: A code change that neither fixes a bug nor adds a feature
- perf: A code change that improves performance
- test: Adding missing tests or correcting existing tests
- chore: Changes to the build process or auxiliary tools
- All submissions require review
- Reviewers should focus on:
- Code quality
- Test coverage
- Documentation
- Performance implications
- Security considerations