added contribution docs

Author: michiosw

CONTRIBUTING.md

@@ -0,0 +1,53 @@
+# Contributing to browser-use MCP Server
+
+### Table of Contents
+
+- [Code of Conduct](#code-of-conduct)
+- [How to Contribute](#how-to-contribute)
+  - [Guidelines for Non-Code Contributions](#guidelines-for-non-code-contributions)
+  - [Reporting Bugs](#reporting-bugs)
+  - [Suggesting Enhancements](#suggesting-enhancements)
+  - [Pull Requests](#pull-requests)
+
+## Code of Conduct
+This project follows a respectful and inclusive environment. By contributing, you agree to maintain a welcoming atmosphere. Any unacceptable behavior should be reported directly to the maintainers.
+
+## How to Contribute
+
+### Guidelines for Non-Code Contributions
+We appreciate your attention to detail. However, minor fixes like typos or grammar corrections should not be submitted individually. Instead, create an issue noting these corrections, and we'll batch them into larger updates.
+
+### Reporting Bugs
+
+#### Before Submitting a Bug
+- Search existing [Issues](https://github.com/co-browser/browser-use-mcp-server/issues) to ensure it hasn't already been reported.
+
+#### How to Submit a Good Bug Report
+- Open a new issue with a descriptive title.
+- Clearly describe the problem, including:
+  - Exact reproduction steps.
+  - Commands or actions taken.
+  - Observed behavior and expected behavior.
+  - Include code snippets, screenshots, or logs formatted using Markdown.
+  - Confirm if the issue is reproducible and under what conditions it occurs.
+
+### Suggesting Enhancements
+
+#### Before Submitting an Enhancement
+- Search existing [Issues](https://github.com/co-browser/browser-use-mcp-server/issues) to avoid duplicates.
+
+#### How to Submit a Good Enhancement Suggestion
+- Clearly and descriptively title your issue.
+- Provide a detailed explanation of the enhancement.
+- Describe current vs. desired behavior.
+- Explain why this enhancement benefits the project and its users.
+- Specify your OS and relevant software versions if applicable.
+
+### Pull Requests
+- Pull requests undergo automated checks, including build and linting. Ensure these checks pass.
+- Ensure your PR addresses the following:
+  - Clearly described purpose and benefits.
+  - Consistent code style and formatting.
+- Clearly document commit messages, providing detailed context for substantial changes.
+- PRs focused solely on formatting without functional improvements will generally be rejected.
+