Hi there! Thank you for being interested in contributing to Nasiko. We're thrilled to have you!
As an open-source platform for building, deploying, and managing AI agents, we are extremely open to contributions, whether they involve new features, improved infrastructure, better documentation, or bug fixes.
To get started with contributing to Nasiko, please:
- Read our Code of Conduct to understand our community standards
- Join our Discord community to discuss ideas and get feedback
- Check the Nasiko documentation to understand the project better
- Follow the guidelines below when submitting your contribution
- Features: New capabilities that enhance Nasiko's agent orchestration and management
- Bug Fixes: Fixes for existing issues in the codebase
- Documentation: Improvements to our docs, examples, and tutorials
- Tests: Additional test coverage for existing functionality
- Infrastructure: Improvements to build, CI/CD, or deployment processes
All pull requests must link to an issue or discussion where a solution has been approved by a maintainer. PRs without prior approval will be closed.
All pull requests should demonstrate meaningful effort and contextual understanding. If the effort required to create a pull request is less than the effort required for maintainers to review it, that contribution should not be submitted. Low-effort drive-by contributions — regardless of how they are produced — often miss the mark in terms of contextual relevance, accuracy, and quality.
The following requirements must be met for all external pull requests:
- Link to an issue or discussion: The pull request must reference an issue or discussion where a solution has been approved by a maintainer
- Fill the PR template: Include all relevant information requested in the pull request template
- Meaningful context: Provide clear explanation of what your change does and why it's needed
- Test coverage: Include tests for new features or fixes when applicable
- Documentation updates: Update docs if your change affects user-facing functionality
Maintainers reserve the right to close PRs without comment if these requirements are not met.
- Discord: Join our Discord community for discussions and quick questions
- GitHub Discussions: Use GitHub discussions for feature ideas and design discussions
- Issues: Check GitHub issues for bugs and feature requests
- Fork the Nasiko repository
- Clone your fork locally
- Create a new branch for your feature:
git checkout -b feature/your-feature-name - Make your changes and commit with clear, descriptive messages
- Push to your fork and submit a pull request
- Follow the existing code style in the repository
- Write clear, descriptive commit messages
- Keep changes focused and avoid mixing multiple features in one PR
- Ensure your code passes any existing tests
We value all contributions, big or small. Our community includes:
Thank you for contributing to Nasiko! 🚀