Contributing to AnswerAgentAI
Welcome to the AnswerAgentAI Alpha Sprint! This guide will help you contribute effectively to our mission of building privacy-first AI tools.
π Getting Startedβ
1. Choose Your Repositoryβ
Visit our organization repositories and pick a project:
- theanswer - Main platform (21kβ)
- aai-browser-sidekick - Chrome extension
- FlowiseChatEmbed - Chat embedding (1.5kβ)
- mcp-inspector - MCP testing tool
- Various MCP servers - HubSpot, Jira, Confluence integrations
2. Find Your First Issueβ
Look for issues tagged with:
beginner- Perfect for first-time contributorsgood first issue- Well-documented starter taskshelp wanted- Community assistance needed
π PR Processβ
Before You Startβ
- Fork the repository you want to contribute to
- Clone your fork locally
- Create a new branch for your feature/fix
- Read the existing code to understand patterns
Development Workflowβ
# Clone your fork
git clone https://github.com/YOUR_USERNAME/REPO_NAME.git
cd REPO_NAME
# Create feature branch
git checkout -b feature/your-feature-name
# Install dependencies
npm install
# or
pnpm install
# Start development server
npm run dev
Making Changesβ
- Follow existing code style - We use ESLint and Prettier
- Write descriptive commit messages
- Test your changes thoroughly
- Update documentation if needed
Commit Message Formatβ
Use conventional commit format:
type: brief description
feat: add new chat sidekick for data analysis
fix: resolve extension popup sizing issue
docs: update API documentation for agents
style: format code according to prettier rules
refactor: improve database query performance
test: add unit tests for chat history
Pull Request Guidelinesβ
1. Create a Quality PRβ
- Title: Clear, descriptive summary
- Description: Explain what you built and why
- Screenshots: For UI changes
- Testing: How you verified it works
2. PR Templateβ
## What I Built
Brief description of your contribution
## Problem It Solves
Explain the specific issue or enhancement
## How It Serves the Mission
Connect to our privacy-first, developer-friendly goals
## Testing Done
- [ ] Local testing completed
- [ ] Edge cases considered
- [ ] Documentation updated
## Screenshots/Video
[Include visual proof of your work]
## Additional Notes
Any special considerations or future improvements
3. Automated Review Processβ
Our system will automatically:
- β Run tests and linting
- π€ Provide AI-suggested improvements
- π Check code coverage
- π Security vulnerability scan
4. Video Requirementβ
Every merged PR requires a 1-3 minute video explaining:
- What you built/fixed
- Problem it solves
- How it serves our mission
- Demo of functionality
Video Guidelinesβ
- Length: 1-3 minutes maximum
- Format: MP4, MOV, or YouTube link
- Quality: Clear audio, visible screen
- Content: Focus on your contribution's impact
π― Contribution Typesβ
Code Contributionsβ
- Bug fixes - Resolve existing issues
- New features - Enhance platform capabilities
- Performance - Optimize speed and efficiency
- Security - Strengthen privacy and safety
Non-Code Contributionsβ
- Documentation - Improve guides and examples
- Testing - Write and improve test coverage
- Design - UI/UX improvements
- Community - Help other contributors