workflows-mcp

# Contributing to workflows-mcp First off, thank you for considering contributing to workflows-mcp! It's people like you that make this project possible. ## How Can I Contribute? ### Reporting Bugs Before creating bug reports, please check existing issues as you might find out that you don't need to create one. When you are creating a bug report, please include as many details as possible using the issue template. ### Suggesting Enhancements Enhancement suggestions are tracked as GitHub issues. When creating an enhancement suggestion, please use the feature request template and include as many details as possible. ### Pull Requests 1. Fork the repo and create your branch from `main`. 2. If you've added code that should be tested, add tests. 3. If you've changed APIs, update the documentation. 4. Ensure the test suite passes. 5. Make sure your code follows the existing style. 6. Issue that pull request! ## Development Process 1. Clone the repository 2. Create a feature branch (`git checkout -b feature/amazing-feature`) 3. Commit your changes (`git commit -m 'Add some amazing feature'`) 4. Push to the branch (`git push origin feature/amazing-feature`) 5. Open a Pull Request ## Code Style - Use clear, descriptive variable names - Comment complex logic - Follow existing patterns in the codebase - Keep functions focused and small ## Commit Messages - Use the present tense ("Add feature" not "Added feature") - Use the imperative mood ("Move cursor to..." not "Moves cursor to...") - Limit the first line to 72 characters or less - Reference issues and pull requests liberally after the first line ## License By contributing, you agree that your contributions will be licensed under the MIT License.