# Contributing to Feature Discussion MCP Server
We love your input! We want to make contributing to this project as easy and transparent as possible, whether it's:
- Reporting a bug
- Discussing the current state of the code
- Submitting a fix
- Proposing new features
- Becoming a maintainer
## Development Setup
1. Fork the repo and create your branch from `main`
2. Install dependencies:
```bash
npm install
```
3. Build the server:
```bash
npm run build
```
4. For development with auto-rebuild:
```bash
npm run watch
```
## Pull Request Process
1. Update the README.md with details of changes to the interface, if applicable
2. Update any relevant documentation
3. Add or update tests for any new functionality
4. Ensure the test suite passes
5. Make sure your code follows our coding standards
6. Get at least one maintainer to review and approve your changes
## Code Style Guidelines
- Use TypeScript for all new code
- Follow the existing code style and formatting
- Use meaningful variable and function names
- Add comments for complex logic
- Keep functions focused and modular
- Write unit tests for new functionality
## Testing Requirements
- Write unit tests for new features
- Ensure all tests pass before submitting PR
- Include both positive and negative test cases
- Test edge cases and error conditions
## Any questions?
Feel free to open an issue for discussion or clarification.
## License
By contributing, you agree that your contributions will be licensed under the same license as the project.