Superjolt MCP Server

# Contributing to Superjolt CLI We love your input! We want to make contributing to Superjolt CLI as easy and transparent as possible. ## What We Accept ✅ **We welcome contributions for:** - Bug fixes - CLI improvements and features - Documentation updates - Test coverage improvements - Performance optimizations ❌ **We generally don't accept:** - Changes to core authentication flow - Features requiring backend API changes - Breaking changes without discussion ## Development Setup 1. Fork the repo and clone your fork 2. Install dependencies: `npm install` 3. Create a branch: `git checkout -b my-feature` 4. Make your changes 5. Run tests: `npm test` 6. Run linter: `npm run lint` 7. Commit your changes 8. Push to your fork and submit a pull request ## Development Commands - `npm run start:dev` - Run CLI in development mode with auto-reload - `npm test` - Run test suite - `npm run lint` - Run ESLint - `npm run build` - Build the CLI ## Pull Request Process 1. Ensure all tests pass 2. Update README.md if you've added new commands 3. Follow existing code style 4. Keep commits focused and atomic ## Reporting Bugs - Use the GitHub issue tracker - Check if the issue already exists - Include reproduction steps - Include your Node.js version and OS ## Feature Requests - Check if already requested - Explain the use case - Be open to discussion ## Questions? Join our [Discord](https://superjolt.com/discord) for help!