# Contributing Guide Thank you for considering contributing to Mono CLI! This document outlines the process and guidelines for contributing. ## Code of Conduct Be respectful, inclusive, and professional in all interactions. ## Getting Started 1. Fork the repository 2. Clone your fork: `git clone https://github.com/your-username/mono-php.git` 3. Create a feature branch: `git checkout -b feature/your-feature-name` 4. Install dependencies: `cd cli && composer install` ## Development Workflow ### Before Making Changes 1. Ensure all tests pass: `composer test` 2. Check code quality: `composer check` ### Making Changes 1. Write clean, well-documented code 2. Follow PSR-12 coding standards 3. Add comprehensive docblocks to all classes and methods 4. Write unit tests for new functionality 5. Update documentation as needed ### Code Style We use Laravel Pint for code formatting: ```bash # Check code style composer lint # Fix code style automatically composer format ``` ### Static Analysis We use PHPStan at level 8 for static analysis: ```bash # Run static analysis composer typecheck ``` ### Refactoring We use Rector for automated refactoring: ```bash # Preview refactoring changes composer refactor:dry # Apply refactoring composer refactor ``` ### Testing Write comprehensive tests for all new features: ```bash # Run all tests composer test # Run tests with coverage composer test:coverage ``` Test requirements: * Unit tests for all new classes and methods * Feature tests for command workflows * Minimum 80% code coverage for new code * All tests must pass before submitting PR ### Quality Checks Run all quality checks before committing: ```bash # Run all checks (test, lint, typecheck, refactor) composer check # Fix all auto-fixable issues composer fix ``` ## Commit Guidelines ### Commit Message Format ``` ():